Re: primary key error message

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2010-01-21T20:51:09Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 21, 2010 at 3:30 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> Here is a small patch that changes the error message
>> 
>>  duplicate key value violates unique constraint "%s"
>> 
>> into
>> 
>>  duplicate key value violates primary key "%s"
>> 
>> when the constraint is in fact a primary key.
>> 
>> Comments?

> Why bother?  And why bother now, when we're in the middle of the last
> CommitFest and trying to move toward a release?

This patch fails to cover all cases (index build being the obvious
omission, but I think there might be other paths as well where the
information is not so readily available).  And I agree with Robert
that the usefulness is at best highly debatable.

			regards, tom lane