Re: use SQL standard error code for nextval

From: Mark Dilger <hornschnorter(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: use SQL standard error code for nextval
Date: 2017-03-09 17:27:07
Message-ID: EF11348D-B998-470E-8A4D-2F047A3F3B39@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Mar 9, 2017, at 7:59 AM, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-03-09 17:28:19 Re: Performance issue after upgrading from 9.4 to 9.6
Previous Message Tom Lane 2017-03-09 17:25:25 Re: partial indexes and bitmap scans