Re: pg_dump bug in 7.3.9 with sequences - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: pg_dump bug in 7.3.9 with sequences
Date
Msg-id 4201EE8D.4010408@familyhealth.com.au
Whole thread Raw
In response to Re: pg_dump bug in 7.3.9 with sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump bug in 7.3.9 with sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: LWLock cache line alignment
Next
From: Oleg Bartunov
Date:
Subject: Re: Crash when inserting gist records, or creating index