Re: Two sequences associated with one identity column

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: "kurt thepw.com" <kurt@thepw.com>, "Colin 't Hart" <colinthart@gmail.com>, PostgreSQL General <pgsql-general@lists.postgresql.org>
Date: 2025-10-29T13:39:19Z
Lists: pgsql-general
On Wednesday, October 29, 2025, Dominique Devienne <ddevienne@gmail.com>
wrote:

> On Wed, Oct 29, 2025 at 2:17 PM kurt thepw.com <kurt@thepw.com> wrote:
> >    If this is a development database, perhaps you can do a schema-only
> pg_dump of it in plain text format, manually edit out the offending second
> sequence from  the resulting SQL file, and restore it into a new database.
>
> I'm surprised the conversation is not more about preventing this from
> ever happening in the first place. Since one cannot get out of it,
> apparently. --DD
>
>
If a reproducer is not offered discussions do tend to focus on fixing the
symptoms since that is what is available to consider.  Not too surprised no
one volunteers to reverse-engineer a reproducer from scratch, given only
the end state.

David J.