I am sorry, I can not reproduce it any more either. I must have made a mistake.
It works perfectly (like the rest of Postgres). Thank you very much, I am sorry
for the waste of time.
Quoting Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Reto Stamm <reto(at)retostamm(dot)com> writes:
> > When I have a sequence like this:
> > CREATE SEQUENCE "test_id_seq" start -32768 increment 1 maxvalue 32767
> > -32768 cache 1;
> > it will show up in schema.txt like this:
> > CREATE SEQUENCE "test_id_seq" start 1 increment 1 maxvalue 32767 minvalue
> > cache 1;
> How old is your Postgres? It works here.
> But note that there is probably also a select setval() for the sequence,
> which is what *really* determines the starting value.
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Neil Conway||Date: 2002-11-07 21:36:07|
|Subject: pg_ctl is fragile|
|Previous:||From: Tom Lane||Date: 2002-11-07 17:57:31|
|Subject: Re: Problem with a sequence being acted on by an on insert rule. |