Re: [HACKERS] use SQL standard error code for nextval

2017-03-09 Thread Tom Lane
Mark Dilger writes: >> On Mar 9, 2017, at 7:59 AM, Peter Eisentraut >> 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

Re: [HACKERS] use SQL standard error code for nextval

2017-03-09 Thread Peter Eisentraut
On 3/9/17 12:27, Mark Dilger wrote: > Perhaps you should add something to the release notes. Somebody could be > testing for the old error code. The release notes will be written when the release is prepared. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development,

Re: [HACKERS] use SQL standard error code for nextval

2017-03-09 Thread Mark Dilger
> On Mar 9, 2017, at 7:59 AM, Peter Eisentraut > 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

Re: [HACKERS] use SQL standard error code for nextval

2017-03-09 Thread Peter Eisentraut
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

[HACKERS] use SQL standard error code for nextval

2017-02-28 Thread Peter Eisentraut
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. -- Peter