Re: [PERFORM] Query with limit goes from few ms to hours

2012-10-23 Thread Steve Crawford
On 10/23/2012 11:33 AM, Kevin Grittner wrote: henk de wit wrote: Well, what do you know! That did work indeed. Immediately after the ANALYZE on that parent table (taking only a few seconds) a fast plan was created and the query executed in ms again. Silly me, I should have tried that earlier.

Re: [PERFORM] Query with limit goes from few ms to hours

2012-10-23 Thread Kevin Grittner
henk de wit wrote: > Well, what do you know! That did work indeed. Immediately after the > ANALYZE on that parent table (taking only a few seconds) a fast > plan was created and the query executed in ms again. Silly me, I > should have tried that earlier. Of course, if your autovacuum settings ar

Re: [PERFORM] Tons of free RAM. Can't make it go away.

2012-10-23 Thread Shaun Thomas
On 10/22/2012 01:44 PM, Claudio Freire wrote: I think, unless it gives you trouble with the page cache, numactl --prefer=+0 should work nicely for postgres overall. Failing that, numactl --interleave=all would, IMO, be better than the system default. Thanks, I'll consider that. FWIW, our curr