Thread: How to trap error: nextval: reached maximum value of sequence

How to trap error: nextval: reached maximum value of sequence

From
Leon Starr
Date:
I want to trap this exception...

ERROR:  nextval: reached maximum value of sequence

...and print a user friendly message.  But I can't figure out what exception code to test
for.  Example:

exception
    when ??? then
        raise exception 'Range too small.';

I looked through the postgres exception codes in the appendix, but couldn't find
the appropriate exception.  WHY don't they match up the error message names???  Is there some
trick to making the connection from a psql error message to the related exception?
(So far I just go with past experience, but it would be nice if there was a system).

Help appreciated!!!

- Leon Starr

Re: How to trap error: nextval: reached maximum value of sequence

From
Merlin Moncure
Date:
On Tue, Jun 21, 2011 at 11:13 PM, Leon Starr <leon_starr@modelint.com> wrote:
> I want to trap this exception...
>
> ERROR:  nextval: reached maximum value of sequence
>
> ...and print a user friendly message.  But I can't figure out what exception code to test
> for.  Example:
>
> exception
>        when ??? then
>                raise exception 'Range too small.';
>
> I looked through the postgres exception codes in the appendix, but couldn't find
> the appropriate exception.  WHY don't they match up the error message names???  Is there some
> trick to making the connection from a psql error message to the related exception?
> (So far I just go with past experience, but it would be nice if there was a system).
>
> Help appreciated!!!

it's object_not_in_prerequisite_state.

A pretty effective way to figure this out is to actually just grep the
code for the error message fragment and see what's being passed to
ereport.

merlin