Thread: View running statements
Is there any way to inspect current running statements (optionally full stack of these statements)? I've found there is error_context_stack variable in each backend, but it seems there is no way to get this variable from another backend. It will be great if Postgres have such kind of mechanism, for instance a system table that consists statements running longer than certain time (5-10 seconds).
In response to Vlad Arkhipov : > Is there any way to inspect current running statements (optionally full > stack of these statements)? I've found there is error_context_stack > variable in each backend, but it seems there is no way to get this > variable from another backend. It will be great if Postgres have such > kind of mechanism, for instance a system table that consists statements > running longer than certain time (5-10 seconds). select * from pg_stat_activity; Andreas -- Andreas Kretschmer Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header) GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net
> In response to Vlad Arkhipov : > >> Is there any way to inspect current running statements (optionally full >> stack of these statements)? I've found there is error_context_stack >> variable in each backend, but it seems there is no way to get this >> variable from another backend. It will be great if Postgres have such >> kind of mechanism, for instance a system table that consists statements >> running longer than certain time (5-10 seconds). >> > > select * from pg_stat_activity; > > > Andreas > It shows only top-level statements. You can see 'select * from f()' in this table but you never see what is actually executing in this function.
Vlad, > It shows only top-level statements. You can see 'select * from f()' in > this table but you never see what is actually executing in this function. Queries executed inside functions are opaque to the stats collector for a variety of technical reasons. Changing this is on the TODO list, but AFAIK nobody is currently working on it. -- Josh Berkus PostgreSQL San Francisco