| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: In progress INSERT wrecks plans on table |
| Date: | 2013-05-02 22:32:20 |
| Message-ID: | kluphf$jn7$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
mark(dot)kirkwood(at)catalyst(dot)net(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-05-02 22:58:00 | Re: matview niceties: pick any two of these three |
| Previous Message | mark.kirkwood | 2013-05-02 22:19:18 | Re: In progress INSERT wrecks plans on table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark.kirkwood | 2013-05-02 22:59:31 | Re: In progress INSERT wrecks plans on table |
| Previous Message | mark.kirkwood | 2013-05-02 22:19:18 | Re: In progress INSERT wrecks plans on table |