| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Dave Owens <dave(at)teamunify(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: query against pg_locks leads to large memory alloc |
| Date: | 2014-08-19 16:40:41 |
| Message-ID: | 1408466441.59082.YahooMailNeo@web122304.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Dave Owens <dave(at)teamunify(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Owens | 2014-08-19 17:14:45 | Re: query against pg_locks leads to large memory alloc |
| Previous Message | Dave Owens | 2014-08-19 15:57:20 | Re: query against pg_locks leads to large memory alloc |