Re: Is necessary to use SEQ_MAXVALUE in pg_dump?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is necessary to use SEQ_MAXVALUE in pg_dump?
Date: 2007-11-05 19:38:35
Message-ID: 26403.1194291515@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> This construct is used to determine if max_value/min_value is used and
> after that pg_dump add NO MAXVALUE to the output instead of the value.
> If I compare it with manual documentation NO MAXVALUE uses default value
> and I do not see any reason to have this code there. I think we can
> remove this code and release dependency on sequence.h.

IIUC you are proposing that it's okay to print random-huge-values in
the dumped CREATE SEQUENCE commands. I don't agree with that.
In particular it would make for a legacy/compatibility issue for
INT64_IS_BROKEN platforms.

A better solution might be to move the declarations of
SEQ_MINVALUE/SEQ_MAXVALUE someplace else.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2007-11-05 19:46:11 Re: Visibility map thoughts
Previous Message Tom Lane 2007-11-05 19:30:13 Re: Postgresql 8.3 beta crash