From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Add some notes about why "ALTER TYPE enum DROP VALUE" is hard.
Date: Tue, 03 Oct 2023 15:41:51 +0000
Message-ID: <E1qnhWx-007Jz0-RP@gemulon.postgresql.org> (raw)
Add some notes about why "ALTER TYPE enum DROP VALUE" is hard.
In hopes of putting these where any would-be implementer is sure to
find them, make a placeholder grammar production for ALTER DROP VALUE
and put them there. This is really just a docs patch, though.
Vik Fearing, with a bit more wordsmithing by me
Discussion: https://postgr.es/m/9fffd149-da0f-0c9c-6745-731fb688642a@postgresfriends.org
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/af3ee8a086ca210d9461f813538d0169dbf07c2c
Modified Files
--------------
src/backend/parser/gram.y | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add some notes about why "ALTER TYPE enum DROP VALUE" is hard.
In-Reply-To: <E1qnhWx-007Jz0-RP@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox