Postgres Pro
Downloads
Home   >   mailing lists

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 1408466441.59082.YahooMailNeo@web122304.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
Tree view 
Dave Owens <dave@teamunify.com> wrote:

> 1358 tables
> 1808 indexes

Hmm, that's not outrageous.  How about long-running transactions?
Please check pg_stat_activity and pg_prepared_xacts for xact_start
or prepared (respectively) values older than a few minutes.  Since
predicate locks may need to be kept until an overlapping
transaction completes, a single long-running transaction can bloat
the lock count.

Also, could you show use the output from?:

  SELECT version();

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

pgsql-performance by date:

Previous
From: Dave Owens
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