Re: pg_locks view versus prepared transactions

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: pg_locks view versus prepared transactions
Дата
Msg-id 20050620200843.GA9005@surnet.cl
обсуждение исходный текст
Ответ на Re: pg_locks view versus prepared transactions  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
Ответы Re: pg_locks view versus prepared transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Mon, Jun 20, 2005 at 03:55:45PM -0400, Merlin Moncure wrote:

> > Ultimately we should maybe even remove PID from pg_locks, but probably
> > for backwards compatibility it'd have to be deprecated for a release
> > or two first.
> 
> It is interesting to note that systems with stats disabled are unable to
> get lock owner information in this case (so what?).

We could make the pg_stat_activity view show information from the
ProcArray shared struct, when stats are disabled.

-- 
Alvaro Herrera (<alvherre[a]surnet.cl>)
"In fact, the basic problem with Perl 5's subroutines is that they're not
crufty enough, so the cruft leaks out into user-defined code instead, by
the Conservation of Cruft Principle."  (Larry Wall, Apocalypse 6)


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

Предыдущее
От: Rohit Gaddi
Дата:
Сообщение: index selection by query planner
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_locks view versus prepared transactions