From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | wrong error message related to unsupported feature |
Date: | 2025-03-18 19:31:16 |
Message-ID: | CAFj8pRDaw=EJyimfB1+JorC3F+P3Vyzy3bkf9doSKFmdpM0QuA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I am playing with new features in Postgres 18.
Maybe I found a bug
(2025-03-18 19:28:06) postgres=# create table foo(a int constraint gzero
check(a > 10) NOT ENFORCED);
CREATE TABLE
(2025-03-18 19:29:37) postgres=# insert into foo values(0);
INSERT 0 1
(2025-03-18 19:29:49) postgres=# insert into foo values(6);
INSERT 0 1
(2025-03-18 19:29:55) postgres=# alter table foo alter constraint gzero
enforced;
ERROR: FOREIGN KEY constraints cannot be marked ENFORCED
LINE 1: alter table foo alter constraint gzero enforced;
I know so altering enforcing constraint is not supported yet, but the error
message is surely wrong
gzero is not foreign key constraint
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2025-03-18 19:31:41 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |
Previous Message | Ilia Evdokimov | 2025-03-18 19:27:47 | Re: [PATCH] Optionally record Plan IDs to track plan changes for a query |