Re: Weird idea for pg_stat_activity

Wouldn't it be weird if an update to pg_stat_activity.current_query
actually ran that query for the selected backend:

UPDATE pg_stat_activity SET current_query = "SELECT 1"
WHERE procpid = 19522;

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Tue, Aug 15, 2006 at 01:29:02AM -0400, Bruce Momjian wrote:
> Wouldn't it be weird if an update to pg_stat_activity.current_query
> actually ran that query for the selected backend:
>
> UPDATE pg_stat_activity SET current_query = "SELECT 1"
> WHERE procpid = 19522;

Interesting thought, though the trick would be having enough control to
be able to inject a query at the right point in the backend's
execution... maybe if there was some kind of 'debug mode' akin to gdb or
the like. Certainly seems like this could be very handy for
trouble-shooting an application you don't have the source for (or one
where the source was such spaghetti that it didn't help much).
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

Bruce,

> Wouldn't it be weird if an update to pg_stat_activity.current_query
> actually ran that query for the selected backend:

Wierd? Yes. Useful? No.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco