From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amaury Dumoulin <amaury@castordoc.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17271: Updating enum columns type fails when constraints exist
Date: Thu, 04 Nov 2021 10:42:38 -0400
Message-ID: <322345.1636036958@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPqDOR9oskSayO-eiR1eyRpYXUqHbrA3rfBS7PSkc79WkS-HGA@mail.gmail.com>
References: <17271-8b4317357c4991e2@postgresql.org>
<CAKFQuwbCVs4Bb4U2Hbgi-1z6uTDHUh8qoW5vr+QmKSaJkEaFZg@mail.gmail.com>
<CAPqDOR9oskSayO-eiR1eyRpYXUqHbrA3rfBS7PSkc79WkS-HGA@mail.gmail.com>
Amaury Dumoulin <amaury@castordoc.com> writes:
> I believe it should fail.
> However the error message should state that the constraint is blocking the
> operation.
> The current error message makes it hard to make a connection to the culprit.
Hmm, that's a reasonable concern, though you didn't make it clear that
that was what you were on about. We could possibly provide an addendum
like "CONTEXT: while processing constraint foo" in this situation.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, amaury@castordoc.com, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17271: Updating enum columns type fails when constraints exist
In-Reply-To: <322345.1636036958@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox