| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | "kurt thepw(dot)com" <kurt(at)thepw(dot)com>, "Colin 't Hart" <colinthart(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Two sequences associated with one identity column |
| Date: | 2025-10-29 13:39:19 |
| Message-ID: | CAKFQuwYcUb=tpK4o-SvBnJ_Q2_Gg2pCS7q6+mosxuH++DEK+bw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, October 29, 2025, Dominique Devienne <ddevienne(at)gmail(dot)com>
wrote:
> On Wed, Oct 29, 2025 at 2:17 PM kurt thepw.com <kurt(at)thepw(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Colin 't Hart | 2025-10-29 13:40:03 | Re: Two sequences associated with one identity column |
| Previous Message | Dominique Devienne | 2025-10-29 13:29:46 | Re: Two sequences associated with one identity column |