Re: reporting reason for certain locks

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: reporting reason for certain locks
Date: 2010-11-25 14:56:27
Message-ID: AANLkTi=3P4k_LoOGzwcHU+iiCg4Dru6pwVTWa_qzWTC0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 25, 2010 at 9:00 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-11-25 15:05:00 Re: reporting reason for certain locks
Previous Message Heikki Linnakangas 2010-11-25 14:36:26 Re: SQL/MED - core functionality