From: | Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr> |
---|---|
To: | "French, Martin" <frenchm(at)cromwell(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [PERFORM] DELETE taking too much memory |
Date: | 2011-07-08 09:50:16 |
Message-ID: | 2882675.kL2jiuFQz7@moltowork |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Friday 08 July 2011 10:31:33 French, Martin wrote:
> If the query planner thinks it has the default amount of memory (128MB)
> and the stats are out of date, then it will by no means be able to plan
> proper execution.
>
> I would recommend setting the effective_cache_size to an appropriate
> value, running "analyze" on both tables with an appropriate stats
> target, and then explaining the query again to see if it's more
> accurate.
Yes, I'll schedule those two to run during the night and repost an explain,
for information. However, we worked around the initial problem by running the
delete in smaller batches.
Thanks.
--
Vincent de Phily
From | Date | Subject | |
---|---|---|---|
Next Message | David Hartveld | 2011-07-08 10:26:06 | Re: Streaming replication on 9.1-beta2 after pg_restore is very slow |
Previous Message | Vincent de Phily | 2011-07-08 09:44:38 | Re: DELETE taking too much memory |
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2011-07-08 10:48:57 | Re: DELETE taking too much memory |
Previous Message | Vincent de Phily | 2011-07-08 09:44:38 | Re: DELETE taking too much memory |