Re: View pg_stat_activity slow to get up to date - Mailing list pgsql-hackers

From Tom Lane
Subject Re: View pg_stat_activity slow to get up to date
Date
Msg-id 10382.1099947542@sss.pgh.pa.us
Whole thread Raw
In response to Re: View pg_stat_activity slow to get up to date  ("D'Arcy J.M. Cain" <darcy@druid.net>)
List pgsql-hackers
"D'Arcy J.M. Cain" <darcy@druid.net> writes:
> Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Increasing the length of pg_stat_activity.current_query...
Next
From: Tom Lane
Date:
Subject: Re: Increasing the length of pg_stat_activity.current_query...