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 20:02:06
Message-ID: 26869.1194292926@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:
> Tom Lane wrote:
>> A better solution might be to move the declarations of
>> SEQ_MINVALUE/SEQ_MAXVALUE someplace else.

> Hmm. It seems better, but it is also hard to find correct place. :( I'm
> thinking put it into c.h.

The idea that was in the back of my mind was pg_config_manual.h,
since these numbers could be seen as configuration constants if
you hold your head at the right angle ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rick Gigger 2007-11-05 20:30:02 Re: should I worry?
Previous Message Zdenek Kotala 2007-11-05 19:52:04 Re: Is necessary to use SEQ_MAXVALUE in pg_dump?