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

From Peter Geoghegan
Subject Re: Patch: show relation and tuple infos of a lock to acquire
Date
Msg-id CAM3SWZTST95+9nNmSv67dxnHc=NDOXoeVDHScKCgLTfm=rZqJg@mail.gmail.com
Whole thread Raw
In response to Re: Patch: show relation and tuple infos of a lock to acquire  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Patch: show relation and tuple infos of a lock to acquire  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
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.


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan
Next
From: Andres Freund
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE