Re: query against pg_locks leads to large memory alloc

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: query against pg_locks leads to large memory alloc
Дата
Msg-id 1408471302.64928.YahooMailNeo@web122302.mail.ne1.yahoo.com
обсуждение исходный текст
Ответ на Re: query against pg_locks leads to large memory alloc  (Dave Owens <dave@teamunify.com>)
Ответы Re: query against pg_locks leads to large memory alloc  (Dave Owens <dave@teamunify.com>)
Список pgsql-performance
Dave Owens <dave@teamunify.com> wrote:

> I wonder if it would be helpful to restart the database, then begin
> gathering information pg_locks while it can still respond to queries.
> I speculate that this is possible because the amount of memory needed
> to query pg_locks continues to grow (around 1900MB now).

If restart is an option, that sounds like a great idea.  If you
could capture the data into tables where we can summarize to
analyze it in a meaningful way, that would be ideal.  Something
like:

CREATE TABLE activity_snap_1 AS SELECT * FROM pg_stat_activity;

Of course, boost the number for each subsequent run.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

Предыдущее
От: Kevin Grittner
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc
Следующее
От: Dave Owens
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc