Re: CREATE DOMAIN create two not null constraints

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CREATE DOMAIN create two not null constraints
Date: 2025-06-02 03:15:19
Message-ID: CACJufxFrAhpTjfsaKWq+uuo=edEsOu0ZO7f_T6dEQh7N7putNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 2, 2025 at 12:13 AM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
>
> Hmm, I think it would be more consistent to reject the case of duplicate
> constraints, instead of silently ignoring it. So you'd do it in the
> loop that checks for constraints before creating anything, like
>
>
> diff --git a/src/backend/commands/typecmds.c b/src/backend/commands/typecmds.c
> index 45ae7472ab5..b5daa61260b 100644
> --- a/src/backend/commands/typecmds.c
> +++ b/src/backend/commands/typecmds.c
> @@ -944,6 +944,12 @@ DefineDomain(ParseState *pstate, CreateDomainStmt *stmt)
> errcode(ERRCODE_SYNTAX_ERROR),
> errmsg("conflicting NULL/NOT NULL constraints"),
> parser_errposition(pstate, constr->location));
> +
> + if (nullDefined)
> + ereport(ERROR,
> + errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
> + errmsg("redundant NOT NULL constraint definition"));
> +
> if (constr->is_no_inherit)
> ereport(ERROR,
> errcode(ERRCODE_INVALID_OBJECT_DEFINITION),

I don't have a preference.
error out would be fine, since it's a corner case.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amul Sul 2025-06-02 03:26:27 Re: Foreign key validation failure in 18beta1
Previous Message jian he 2025-06-02 03:13:20 Re: ALTER TABLE ALTER CONSTRAINT misleading error message