From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Update a code comment |
Date: | 2025-03-19 09:45:01 |
Message-ID: | E1tupyv-003FHH-1Z@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Update a code comment
The comment explained that ALTER TABLE ADD CONSTRAINT USING INDEX is
only supported with a btree index. (This is not being changed.) The
reason is to keep upgrades robust, as explained there. The other part
of the comment, that btree is the only unique index kind anyway, is
somewhat less true as we're trying to enable unique indexes other than
btree, and it's irrelevant to this check. There is a check for
indisunique earlier already. So just remove this part of the comment.
Author: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330(at)enterprisedb(dot)com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/190dc27998d5b7b4c36e12bebe62f7176f4b4507
Modified Files
--------------
src/backend/parser/parse_utilcmd.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2025-03-19 13:04:30 | pgsql: meson: Flush stdout in testwrap |
Previous Message | Peter Eisentraut | 2025-03-19 06:08:40 | pgsql: extension_control_path |