Re: BUG #6275: Horrible performance regression

Поиск
Список
Период
Сортировка
От Mark Kirkwood
Тема Re: BUG #6275: Horrible performance regression
Дата
Msg-id 4EAF74F6.6020200@catalyst.net.nz
обсуждение исходный текст
Ответ на BUG #6275: Horrible performance regression  ("Finlay Thompson" <finlay@dragonfly.co.nz>)
Ответы Re: BUG #6275: Horrible performance regression  (Finlay Thompson <finlay@dragonfly.co.nz>)
Список 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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #6280: adminpack.sql not found after postgresql-contrib has been installed
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Hanging with pg_restore and large objects