From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: reporting reason for certain locks |
Date: | 2010-11-25 14:00:45 |
Message-ID: | 1290693417-sup-6729@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
If so, that's great -- but we'd be getting a bit ahead of ourselves.
Because while we do have the locking details available some of the time,
it's not easy to figure out what they are; and the rest of the time, it
just isn't available.
So I'm proposing a mechanism for this information to be available in the
first place. When this is done we can talk about some nice user
interface for it.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2010-11-25 14:16:27 | Re: SQL/MED - core functionality |
Previous Message | Fujii Masao | 2010-11-25 13:47:12 | Re: libpq changes for synchronous replication |