On Tue, Mar 18, 2014 at 5:51 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvhe...@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?
The message for exclusive lock on tuple print the database information. "LOG: process 3012 still waiting for ExclusiveLock on tuple (0,1) of relation 57 499 of database 12045 after 1014.000 ms" I think database related info (dbid) will be printed in other Lock related messages as well, for example: LOG: process 1332 still waiting for AccessExclusiveLock on relation 16384 of da tabase 12077 after 1014.000 ms I believe the reason is to uniquely identify a tuple on which transaction is waiting. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers