Re: Making serial survive pg_dump - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Making serial survive pg_dump
Date
Msg-id 06ab01c21323$9a445db0$fe01a8c0@jester
Whole thread Raw
In response to Making serial survive pg_dump  ("Rod Taylor" <rbt@zort.ca>)
Responses Re: Making serial survive pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Normally I'd agree, but I've found a few people who use normal
sequence operations with serial sequences.  That is, they track down
the name and use it.

I'd prefer to force these people to make it manually, but would be
surprised if that was a concensus.

--
Rod
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Rod Taylor" <rbt@zort.ca>
Cc: "Hackers List" <pgsql-hackers@postgresql.org>
Sent: Thursday, June 13, 2002 5:41 PM
Subject: Re: [HACKERS] Making serial survive pg_dump


> "Rod Taylor" <rbt@zort.ca> writes:
> > Ok, keeping the setval is appropriate.  Are there any problems
with a
> > SERIAL(<sequence name>) implementation?
>
> What for?  The sequence name is an implementation detail, not
something
> we want to expose (much less let users modify).
>
> regards, tom lane
>



pgsql-hackers by date:

Previous
From: Mike Mascari
Date:
Subject: Non-standard feature request
Next
From: "Rod Taylor"
Date:
Subject: Re: Making serial survive pg_dump