pgsql: Add some notes about why "ALTER TYPE enum DROP VALUE" is hard.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Add some notes about why "ALTER TYPE enum DROP VALUE" is hard.
Date: 2023-10-03 15:41:51
Message-ID: E1qnhWx-007Jz0-RP@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2023-10-03 15:55:04 pgsql: Remove IndexInfo.ii_OpclassOptions field
Previous Message Robert Haas 2023-10-03 15:01:18 pgsql: In basebackup.c, refactor to create read_file_data_into_buffer.