Re: pgsql-server/src/backend commands/sequence.c p ...

Shouldn't this patch need some pg_dump changes? And doc changes? Maybe
even psql changes?

How is NO MAXVALUE and NO MINVALUE stored in the database? How are they
recreated that way after a dump?

Chris

> -----Original Message-----
> From: pgsql-committers-owner(at)postgresql(dot)org
> [mailto:pgsql-committers-owner(at)postgresql(dot)org]On Behalf Of Bruce Momjian
> - CVS
> Sent: Thursday, 13 February 2003 1:25 PM
> To: pgsql-committers(at)postgresql(dot)org
> Subject: [COMMITTERS] pgsql-server/src/backend commands/sequence.c p ...
>
>
> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: momjian(at)postgresql(dot)org 03/02/13 00:25:25
>
> Modified files:
> src/backend/commands: sequence.c
> src/backend/parser: gram.y
>
> Log message:
> Adds in NO MAXVALUE and NO MINVALUE options for create
> sequence per 200X
> spec, which will also make alter sequence a touch easier.
>
> sequence.c init_params() will check for settings which have been
> defined twice, and complain.
>
> Rod Taylor
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>