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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Christian Kruse <christian(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch: show relation and tuple infos of a lock to acquire
Date: 2014-01-02 09:40:38
Message-ID: CAM3SWZTST95+9nNmSv67dxnHc=NDOXoeVDHScKCgLTfm=rZqJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 2, 2014 at 12:56 AM, Andres Freund <andres(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-01-02 09:49:27 Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Previous Message Andres Freund 2014-01-02 09:27:57 Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan