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

From Peter Eisentraut
Subject Re: [HACKERS] use SQL standard error code for nextval
Date
Msg-id fa0f50f8-5af9-b70d-e7c7-54a6110401cd@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] use SQL standard error code for nextval  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] use SQL standard error code for nextval  (Mark Dilger <hornschnorter@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] [bug fix] dblink leaks unnamed connections
Next
From: Stephen Frost
Date:
Subject: [HACKERS] partial indexes and bitmap scans