Re: Making serial survive pg_dump

From: "Rod Taylor" <rbt(at)zort(dot)ca>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hackers List" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making serial survive pg_dump
Date: 2002-06-13 21:45:14
Message-ID: 06ab01c21323$9a445db0$fe01a8c0@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rod Taylor" <rbt(at)zort(dot)ca>
Cc: "Hackers List" <pgsql-hackers(at)postgresql(dot)org>
Sent: Thursday, June 13, 2002 5:41 PM
Subject: Re: [HACKERS] Making serial survive pg_dump

> "Rod Taylor" <rbt(at)zort(dot)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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-06-13 21:52:34 Re: Making serial survive pg_dump
Previous Message jack 2002-06-13 21:41:17 Re: [HACKERS] PATCH SSL_pending() checks in libpq/fe-misc.c