Re: Bug with rename bigserial column - Mailing list pgsql-general

From Nigel J. Andrews
Subject Re: Bug with rename bigserial column
Date
Msg-id Pine.LNX.4.21.0401111309340.29683-100000@ponder.fairway2k.co.uk
Whole thread Raw
In response to Re: Bug with rename bigserial column  (Richard Huxton <dev@archonet.com>)
Responses Re: Bug with rename bigserial column  (Richard Huxton <dev@archonet.com>)
List pgsql-general
On Sun, 11 Jan 2004, Richard Huxton wrote:

> On Saturday 10 January 2004 21:31, D. Dante Lorenso wrote:
> > I just ran into a dump/restore problem with a bigserial column
> > on a renamed table.
> [snip]
> > I've corrected the problem manually, but it does seem like a bug
> > somewhere.
>
> Sounds like a bug. You might want to have a look and see if it's restoring the
> value of the old or new sequence.
>
> There's a bug form on the website or a -bugs mailing list if you prefer that.
> A short example showing the sequence of commands will almost certainly help
> too, as will the version of PG you're running.

I think previous discussions on this couldn't decide between not renaming the
underlying sequence and the one where the sequence is also renamed when the
table is.

Of course in this instance it's slightly different in that it does sound like a
bug of the dump/restore process with the not renaming sequence behaviour
employed.

I think this applies to 7.4.x as well as 7.3.x but could swear to it.


--
Nigel J. Andrews


pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Bug with rename bigserial column
Next
From: Jean-Michel POURE
Date:
Subject: Re: Is my MySQL Gaining ?