Re: reporting reason for certain locks

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 15:05:00
Message-ID: 1290697464-sup-3004@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Robert Haas's message of jue nov 25 11:56:27 -0300 2010:

> 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.

Ah, I was looking for a SQL-callable function :-) Hmm, maybe this would
work.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-11-25 15:06:39 Re: Horizontal Write Scaling
Previous Message Robert Haas 2010-11-25 14:56:27 Re: reporting reason for certain locks