Re: ALTER TABLE ALTER CONSTRAINT misleading error message

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER TABLE ALTER CONSTRAINT misleading error message
Date: 2025-07-03 09:31:12
Message-ID: 202507030931.rlhp2wzdtnhc@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Jul-03, Fujii Masao wrote:

> If we go with it, I’m slightly inclined to add [ ENFORCED ] to
> the CREATE TRIGGER syntax in the docs. Without that, users might be confused
> or raise concerns that CREATE CONSTRAINT TRIGGER accepts an option
> (i.e., ENFORCED) that isn't actually documented in the syntax.
> But if you think this is overkill, I'm ok not to update the syntax in the docs.

Yeah, makes sense. We document noise words for other commands as well,
so I added that and pushed.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Every machine is a smoke machine if you operate it wrong enough."
https://twitter.com/libseybieda/status/1541673325781196801

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-07-03 09:37:16 Re: Logical Replication of sequences
Previous Message Andrei Lepikhov 2025-07-03 09:23:06 Re: MergeJoin beats HashJoin in the case of multiple hash clauses