Re: PG connections going to 'waiting'

Поиск
Список
Период
Сортировка
От Chris Barnes
Тема Re: PG connections going to 'waiting'
Дата
Msg-id BLU149-W3025BA677F7C0588AD598AD4ED0@phx.gbl
обсуждение исходный текст
Ответ на Re: PG connections going to 'waiting'  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: PG connections going to 'waiting'
Список 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.mckay@gmail.com
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] PG connections going to 'waiting'
> Date: Sat, 5 Sep 2009 15:24:55 -0400
> From: tgl@sss.pgh.pa.us
>
> Alan McKay <alan.mckay@gmail.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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


Faster Hotmail access now on the new MSN homepage.

В списке pgsql-general по дате отправления:

Предыдущее
От: Andy Colson
Дата:
Сообщение: Re: easy task: concurrent select-updates
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Getting "insufficient data left in message" on copy with binary