Re: Minor bug affecting ON CONFLICT lock wait log messages - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Minor bug affecting ON CONFLICT lock wait log messages
Date
Msg-id 20160315153117.GB3127@tamriel.snowman.net
Whole thread Raw
In response to Re: Minor bug affecting ON CONFLICT lock wait log messages  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Minor bug affecting ON CONFLICT lock wait log messages
List pgsql-hackers
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> Stephen Frost wrote:
> > * Julien Rouhaud (julien.rouhaud@dalibo.com) wrote:
>
> > XLTW_InsertIndexUnique is used when building a unique index, but this is
> > just a check, and more to the point, it's actually a re-check of what
> > we're doing in nbinsert.c where we're already using XLTW_InsertIndex.
> >
> > We wouldn't want to end up returning different error messages for the
> > same command under the same conditions just based, which is what we'd
> > potentially end up doing if we used XLTW_InsertIndexUnique here.
>
> Perhaps we need a new value in that enum, so that the context message is
> specific to the situation at hand?

Maybe, but that would require a new message and new translation and just
generally doesn't seem like something we'd want to back-patch for a
bugfix.  As such, if someone's interested, they could certainly propose
it to go into HEAD, but I'm not going to look at making those kinds of
changes for this bugfix.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Robert Haas
Date:
Subject: PostgreSQL 9.6 Feature Freeze - April 8, 2016