Re: query against pg_locks leads to large memory alloc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave Owens <dave@xxxxxxxxxxxxx> 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


-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance





[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux