Re: View pg_stat_activity slow to get up to date

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: View pg_stat_activity slow to get up to date
Date: 2004-11-08 20:59:02
Message-ID: 10382.1099947542@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"D'Arcy J.M. Cain" <darcy(at)druid(dot)net> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> ISTM that what you have here is a bad substitute for using user locks
>> (see contrib/userlock/).

> Perhaps. I assume that the lock is automatically released when the
> holder closes its connection to the database, right? If so then that's
> what I need.

Right, user locks will be dropped automatically at backend exit
(otherwise their management is entirely in your hands).

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-11-08 21:00:15 Re: Increasing the length of pg_stat_activity.current_query...
Previous Message Greg Stark 2004-11-08 20:31:16 Re: Increasing the length of pg_stat_activity.current_query...