| From: | Dave Owens <dave(at)teamunify(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, 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 18:28:58 |
| Message-ID: | CA+OQrzi1S7k6tU8fept8D4=iD7LgOnv3kRAmp2RnmrDrtNJpJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 19, 2014 at 11:01 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> 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 -
Would the you or the list be interested in snapshots of pg_locks as well?
I can take a restart tonight and get this going on a half-hourly basis
(unless you think more frequent snaps would be useful).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2014-08-19 18:43:30 | Re: query against pg_locks leads to large memory alloc |
| Previous Message | Kevin Grittner | 2014-08-19 18:01:42 | Re: query against pg_locks leads to large memory alloc |