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>, "jian he" <jian(dot)universality(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER TABLE ALTER CONSTRAINT misleading error message
Date: 2025-06-27 13:30:43
Message-ID: 0ef5121b-f0e8-49f3-9810-3a349c174c6b@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-06-27, Fujii Masao wrote:

> To make this distinction, I just started thinking it's better to raise
> the error
> in ATExecAlterConstraint() rather than in gram.y. I've attached a draft
> patch that
> follows this approach.

Hmm I don't like this very much, it feels very kludgy. I think if we want to consider this in scope for pg18 I would much prefer to use the patch I mentioned near the beginning of the thread.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timur Magomedov 2025-06-27 14:24:41 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Previous Message Tatsuo Ishii 2025-06-27 13:14:54 Re: PG18 protocol version