From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Weird idea for pg_stat_activity |
Date: | 2006-08-15 14:52:03 |
Message-ID: | 20060815145202.GN27928@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | AgentM | 2006-08-15 14:53:14 | Re: An Idea for planner hints |
Previous Message | Bruce Momjian | 2006-08-15 14:45:22 | Re: [Patch] - Fix for bug #2558, InitDB failed to run |