Re: query against pg_locks leads to large memory alloc - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: query against pg_locks leads to large memory alloc
Date
Msg-id 1408471302.64928.YahooMailNeo@web122302.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: query against pg_locks leads to large memory alloc  (Dave Owens <dave@teamunify.com>)
Responses Re: query against pg_locks leads to large memory alloc
List 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 by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: query against pg_locks leads to large memory alloc
Next
From: Dave Owens
Date:
Subject: Re: query against pg_locks leads to large memory alloc