Re: [HACKERS] use SQL standard error code for nextval - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: [HACKERS] use SQL standard error code for nextval
Date
Msg-id EF11348D-B998-470E-8A4D-2F047A3F3B39@gmail.com
Whole thread Raw
In response to Re: [HACKERS] use SQL standard error code for nextval  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] use SQL standard error code for nextval
Re: [HACKERS] use SQL standard error code for nextval
List pgsql-hackers
> On Mar 9, 2017, at 7:59 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>
> On 2/28/17 22:15, Peter Eisentraut wrote:
>> The SQL standard defines a separate error code for nextval exhausting
>> the sequence space.  I haven't found any discussion of this in the
>> archives, so it seems this was just not considered or not yet in
>> existence when the error codes were introduced.  Here is a patch to
>> correct it.
>
> committed

Perhaps you should add something to the release notes.  Somebody could be
testing for the old error code.

Mark Dilger


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] partial indexes and bitmap scans
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Performance issue after upgrading from 9.4 to 9.6