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 8918.1099937254@sss.pgh.pa.us
Whole thread Raw
In response to View pg_stat_activity slow to get up to date  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Responses 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:
> I checked the FAQ and docs but haven't found anything definitive.  This
> is my SQL test script:

> SELECT pg_backend_pid();
> SELECT * FROM pg_stat_activity order by procpid;

> When I run psql reading that I find that my backend procpid is not in
> the list.  I know that I can see it if I can introduce a little sleep (1
> second) between the connection and the reading of pg_stat_activity.

ISTM that what you have here is a bad substitute for using user locks
(see contrib/userlock/).
        regards, tom lane


pgsql-hackers by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: View pg_stat_activity slow to get up to date
Next
From: oozmen@cs.uwaterloo.ca
Date:
Subject: How to create/initialize/access an execution plan