| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump bug in 7.3.9 with sequences |
| Date: | 2005-02-03 09:27:41 |
| Message-ID: | 4201EE8D.4010408@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> pg_dump will just emit "create table t1 (f1 serial)" with no hint that
> the sequence ought to be set to CYCLE mode. I'm not sure about an
> appropriate fix offhand --- we can't very well use ALTER SEQUENCE in
> just this way in the dump, because of the risk of the sequence name
> being possibly different at reload. (Come to think of it, we are not
> very good about propagating GRANTs on the sequence either, because of
> the same risk.)
I suggest some time ago an alternative syntax for ALTER SEQUENCE. So,
you'd have:
ALTER SEQUENCE seqname ...
or
ALTER SEQUENCE ON table.column ...
or something.
Then it would be similar to have pg_get_serial_sequence() works.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2005-02-03 09:34:48 | Re: Crash when inserting gist records, or creating index |
| Previous Message | Peter Eisentraut | 2005-02-03 06:59:19 | Re: libpq API incompatibility between 7.4 and 8.0 |