To: pgsql-performance@postgresql.org
From: Thomas Kellerer <spam_eater@gmx.net>
Subject: Re: In progress INSERT wrecks plans on table
Date: Fri, 03 May 2013 00:32:20 +0200
Lines: 10
Message-ID: <kluphf$jn7$1@ger.gmane.org>
References: <5179E77B.7050601@catalyst.net.nz>
	<5179ECC5.2010206@archidevsys.co.nz>
	<5179F259.3010509@catalyst.net.nz>
	<5179F5C6.8070702@archidevsys.co.nz>
	<5180E3C8.3010201@catalyst.net.nz> <2121.1367417215@sss.pgh.pa.us>
	<5181B80D.70404@catalyst.net.nz>
	<CA+U5nMKYYZDekhtxz1E1B11dAm9UJoHBQHrB6DiiZDJo3fLd0Q@mail.gmail.com>
	<916bff05a5ab130c76d7835abbaf7762.squirrel@mail.catalyst.net.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
	rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
In-Reply-To: <916bff05a5ab130c76d7835abbaf7762.squirrel@mail.catalyst.net.nz>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

mark.kirkwood@catalyst.net.nz wrote on 03.05.2013 00:19:
> I think the idea of telling postgres that we are doing a load is probably
> the wrong way to go about this. We have a framework that tries to
> automatically figure out the best plans...I think some more thought about
> how to make that understand some of the more subtle triggers for a
> time-to-do-new-plans moment is the way to go. I understand this is
> probably hard - and may imply some radical surgery to how the stats
> collector and planner interact.

I wonder if "freezing" (analyze, then disable autovacuum) the statistics for the large number of rows would work.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance