MIME-Version: 1.0
In-Reply-To: <CAFCRh-8gM44R=V_TonSZmGLvZRT9wrtNXYCAXFC-aArSNnsm_w@mail.gmail.com>
References: <CAMon-aTbZC5k2pLpijk5x+h__LV08DzpoJtHBgZGkOKJNJ91pw@mail.gmail.com>
 <aQICcMvkp96kenL8@depesz.com> <CAMon-aTMgbwC9j-wY8iX5kZ4=KXzCXc-Wpwx3viid8hQ_bJkoQ@mail.gmail.com>
 <aQIDbBO0nJTiMd5C@depesz.com> <CAMon-aT-DyO6mesMub_dYTo+mZ6yQ8kHMrMCCz19qrV4rUKiZQ@mail.gmail.com>
 <BN8PR07MB5905EB3838C147873902EA1DD3FAA@BN8PR07MB5905.namprd07.prod.outlook.com>
 <CAFCRh-8gM44R=V_TonSZmGLvZRT9wrtNXYCAXFC-aArSNnsm_w@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 29 Oct 2025 09:39:19 -0400
Message-ID: <CAKFQuwYcUb=tpK4o-SvBnJ_Q2_Gg2pCS7q6+mosxuH++DEK+bw@mail.gmail.com>
Subject: Re: Two sequences associated with one identity column
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>
Content-Type: multipart/alternative; boundary="0000000000006e522906424c4254"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwYcUb%3DtpK4o-SvBnJ_Q2_Gg2pCS7q6%2BmosxuH%2B%2BDEK%2Bbw%40mail.gmail.com>
Precedence: bulk

--0000000000006e522906424c4254
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, October 29, 2025, Dominique Devienne <ddevienne@gmail.com>
wrote:

> On Wed, Oct 29, 2025 at 2:17=E2=80=AFPM kurt thepw.com <kurt@thepw.com> w=
rote:
> >    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 secon=
d
> 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.

--0000000000006e522906424c4254
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, October 29, 2025, Dominique Devienne &lt;<a href=3D"mailto:dd=
evienne@gmail.com">ddevienne@gmail.com</a>&gt; wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On Wed, Oct 29, 2025 at 2:17=E2=80=AFPM kurt <a href=3D"http:=
//thepw.com" target=3D"_blank">thepw.com</a> &lt;<a href=3D"mailto:kurt@the=
pw.com">kurt@thepw.com</a>&gt; wrote:<br>
&gt;=C2=A0 =C2=A0 If this is a development database, perhaps you can do a s=
chema-only pg_dump of it in plain text format, manually edit out the offend=
ing second sequence from=C2=A0 the resulting SQL file, and restore it into =
a new database.<br>
<br>
I&#39;m surprised the conversation is not more about preventing this from<b=
r>
ever happening in the first place. Since one cannot get out of it,<br>
apparently. --DD<br><br>
</blockquote><div><br></div><div>If a reproducer is not offered discussions=
 do tend to focus on fixing the symptoms since that is what is available to=
 consider.=C2=A0 Not too surprised no one volunteers to reverse-engineer a =
reproducer from scratch, given only the end state.</div><div><br></div><div=
>David J.</div><div>=C2=A0</div>

--0000000000006e522906424c4254--