Re: use SQL standard error code for nextval

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: use SQL standard error code for nextval
Date: 2017-03-09 15:59:02
Message-ID: fa0f50f8-5af9-b70d-e7c7-54a6110401cd@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-03-09 16:01:21 partial indexes and bitmap scans
Previous Message Tom Lane 2017-03-09 15:54:11 Re: [bug fix] dblink leaks unnamed connections