From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Finlay Thompson <finlay(at)dragonfly(dot)co(dot)nz> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6275: Horrible performance regression |
Date: | 2011-11-01 04:26:30 |
Message-ID: | 4EAF74F6.6020200@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 28/10/11 15:42, Finlay Thompson wrote:
> After upgrading the postgresql*-8.4 packages on ubuntu, to version 8.4.9,
> the script suddenly stopped working, and consuming all the ram (16GB) on the
> computer (i7).
>
>
If there is one query exhausting all ram, then it could be tricky to
catch it in the logs (log duration and friends log the query time on
completion... which might be never). If you have vm.overcommit_memory
set to 2 then you may get the offending statement in the log when the
postgres backend errors out with ENOMEM.
If you know the approx time at which memory starts filling up then
getting (most of) the query text from pg_stat_activity would enable you
to track down the offending sql in your load script.
regards
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-11-01 04:43:13 | Re: Hanging with pg_restore and large objects |
Previous Message | Tom Lane | 2011-11-01 04:18:49 | Re: BUG #6280: adminpack.sql not found after postgresql-contrib has been installed |