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 20140102085630.GC2683@awork2.anarazel.de
Whole thread Raw
In response to Re: Patch: show relation and tuple infos of a lock to acquire  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Patch: show relation and tuple infos of a lock to acquire
List pgsql-hackers
On 2013-12-31 13:56:53 -0800, Peter Geoghegan wrote:
> ISTM that you should be printing just the value and the unique index
> there, and not any information about the tuple proper. Doing any less
> could be highly confusing.

I agree that the message needs improvement, but I don't agree that we
shouldn't lock the tuple's location. If you manually investigate the
situation that's where you'll find the conflicting tuple - I don't see
what we gain by not logging the ctid.

Greetings,

Andres Freund

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: more psprintf() use
Next
From: Andres Freund
Date:
Subject: Re: Patch: show relation and tuple infos of a lock to acquire