Re: Patch: show relation and tuple infos of a lock to acquire - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Patch: show relation and tuple infos of a lock to acquire
Date
Msg-id 20140318002426.GW16438@awork2.anarazel.de
Whole thread Raw
In response to Re: Patch: show relation and tuple infos of a lock to acquire  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2014-03-17 20:21:18 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > 1. MyProcPort contains the database name; no need for the
> > get_database_name() call in there.
> 
> Wait. A. Minute.  This patch wants to print the current database name in
> the message?  What on earth for?  What other error messages do you see
> doing that?

+many. At least Christian and I argued against it on those grounds. I am
not sure why Amit had at least temporarily won that battle.

Anybody wanting information about which database a message happened in
should just add %b to log_line_prefix.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch: show relation and tuple infos of a lock to acquire
Next
From: Craig Ringer
Date:
Subject: Re: pg_dump without explicit table locking