From: Vincent de Phily <vincent.dephily@mobile-devices.fr>
To: French, Martin <frenchm@cromwell.co.uk>
Cc: pgsql-general@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] DELETE taking too much memory
Date: Fri, 08 Jul 2011 11:50:16 +0200
Message-ID: <2882675.kL2jiuFQz7@moltowork> (raw)
In-Reply-To: <81976671721DF04B9DCA6ECD87941A402B40FBD5@roundway.Cromwell-tools.co.uk>
References: <CAHdkwt5b=g_Nj0mogB-8u62U9wEB1KdCbPiBkJKGJyjM4q=FvQ@mail.gmail.com>
<6960221.CJCJgSSb5M@moltowork>
<81976671721DF04B9DCA6ECD87941A402B40FBD5@roundway.Cromwell-tools.co.uk>
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
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: vincent.dephily@mobile-devices.fr, frenchm@cromwell.co.uk, pgsql-general@postgresql.org
Subject: Re: [PERFORM] DELETE taking too much memory
In-Reply-To: <2882675.kL2jiuFQz7@moltowork>
* 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