Horton
Menu

Re: ALTER TABLE ALTER CONSTRAINT misleading error message

Álvaro Herrera <alvherre@kurilemu.de>

View thread
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: jian he <jian.universality@gmail.com>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-03T09:31:12Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix bogus grammar for a CREATE CONSTRAINT TRIGGER error

  2. Fix error message for ALTER CONSTRAINT ... NOT VALID