On Thu, Jan 2, 2014 at 12:56 AM, Andres Freund <and...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
