]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 27 Sep 2017 20:14:37 +0000 (16:14 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 27 Sep 2017 20:14:37 +0000 (16:14 -0400)
commit93a1af0b3f63838774a9e524589344c3d44c867d
treee12c9d5a1331dd100a8a15b72962732e41dd03a6
parent4d5d08c1cd52add02bdfadc00854135a3b6c88f6
Revert to 9.6 treatment of ALTER TYPE enumtype ADD VALUE.

This reverts commit 15bc038f9, along with the followon commits 1635e80d3
and 984c92074 that tried to clean up the problems exposed by bug #14825.
The result was incomplete because it failed to address parallel-query
requirements.  With 10.0 release so close upon us, now does not seem like
the time to be adding more code to fix that.  I hope we can un-revert this
code and add the missing parallel query support during the v11 cycle.

Back-patch to v10.

Discussion: https://postgr.es/m/20170922185904.1448.16585@wrigleys.postgresql.org
doc/src/sgml/ref/alter_type.sgml
src/backend/access/transam/xact.c
src/backend/catalog/pg_enum.c
src/backend/commands/typecmds.c
src/backend/tcop/utility.c
src/backend/utils/adt/enum.c
src/backend/utils/errcodes.txt
src/include/catalog/pg_enum.h
src/include/commands/typecmds.h
src/test/regress/expected/enum.out
src/test/regress/sql/enum.sql