Re: Patch: show relation and tuple infos of a lock to acquire

On 2014-01-02 01:40:38 -0800, Peter Geoghegan wrote:
> On Thu, Jan 2, 2014 at 12:56 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> > 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.
> 
> I suppose so, but the tuple probably isn't going to be visible anyway,
> at least when the message is initially logged.

But that's the case for all these, otherwise we wouldn't wait on the
row.

Greetings,

Andres Freund

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