Re: Bug with rename bigserial column

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Bug with rename bigserial column
Date: 2004-01-11 13:14:32
Message-ID: Pine.LNX.4.21.0401111309340.29683-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jean-Michel POURE 2004-01-11 13:33:54 Re: [GENERAL] Is my MySQL Gaining ?
Previous Message Richard Huxton 2004-01-11 09:41:37 Re: Bug with rename bigserial column