pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-performance@postgresql.org
Subject: Re: In progress INSERT wrecks plans on table
Date: Fri, 03 May 2013 00:32:20 +0200
Message-ID: <kluphf$jn7$1@ger.gmane.org> (raw)
In-Reply-To: <916bff05a5ab130c76d7835abbaf7762.squirrel@mail.catalyst.net.nz>
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>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

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



view thread (42+ messages)  latest in thread

Message-ID: <kluphf$jn7$1@ger.gmane.org>
Permalink:  ../kluphf$jn7$1@ger.gmane.org/
Also on:    postgresql.org/message-id/kluphf$jn7$1@ger.gmane.org

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: spam_eater@gmx.net
  Subject: Re: In progress INSERT wrecks plans on table
  In-Reply-To: <kluphf$jn7$1@ger.gmane.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox