From: | Chris Barnes <compuguruchrisbarnes(at)hotmail(dot)com> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <alan(dot)mckay(at)gmail(dot)com> |
Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PG connections going to 'waiting' |
Date: | 2009-09-05 23:41:42 |
Message-ID: | BLU149-W3025BA677F7C0588AD598AD4ED0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Is the any way to look at the statistics on the name of table, length and type over a period of time?
Or, would we have to use munin and capture these stats for analysis later?
Chris
> To: alan(dot)mckay(at)gmail(dot)com
> CC: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] PG connections going to 'waiting'
> Date: Sat, 5 Sep 2009 15:24:55 -0400
> From: tgl(at)sss(dot)pgh(dot)pa(dot)us
>
> Alan McKay <alan(dot)mckay(at)gmail(dot)com> writes:
> >> pg_locks? Somebody taking exclusive lock on a widely-used table might
> >> explain that.
>
> > OK, in theory we could do the following, no?
>
> > Use our PITR logs to restore a tertiary system to the point when we
> > were having the problem (we have a pretty wide 2 or 3 hour window to
> > hit), then query the pg_locks table on that system?
>
> No, that wouldn't tell you a single thing. pg_locks is a dynamic view
> of current system state. You would have to look at it while having
> the problem.
>
> regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
_________________________________________________________________
Click less, chat more: Messenger on MSN.ca
http://go.microsoft.com/?linkid=9677404
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-06 00:01:42 | Re: Getting "insufficient data left in message" on copy with binary |
Previous Message | Andy Colson | 2009-09-05 20:14:12 | Re: easy task: concurrent select-updates |