On Thu, Nov 25, 2010 at 9:00 AM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Excerpts from Robert Haas's message of mar nov 23 00:08:54 -0300 2010: > >> How about publishing additional details to pg_stat_activity via >> pgstat_report_waiting()? > > I'm not sure what you mean here. Are you suggesting we should create a > new function with that name to report the reason for the lock?
No, what I was suggesting was taking the existing function: extern void pgstat_report_waiting(bool waiting); ...and instead doing something like this: extern void pgstat_report_waiting(char *reason); ...and then arrange to pass the reason via the eponymous argument. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
