From: | Reto Stamm <reto(at)retostamm(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Sequence Start number not dumped correctly |
Date: | 2002-11-07 18:56:25 |
Message-ID: | 1036695385.3dcab759e9eff@webmail.spamcop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello Tom,
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.
Best regards
--reto
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
> minvalue
> > -32768 cache 1;
>
> > it will show up in schema.txt like this:
>
> > CREATE SEQUENCE "test_id_seq" start 1 increment 1 maxvalue 32767 minvalue
> -32768
> > 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
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-11-07 21:36:07 | pg_ctl is fragile |
Previous Message | Tom Lane | 2002-11-07 17:57:31 | Re: Problem with a sequence being acted on by an on insert rule. |