Partially restore comments discussing enum renumbering hazards.
As noted by Tom Lane, commit 813fb0315587d32e3b77af1051a0ef517d187763
was overly optimistic about how safe it is to concurrently change
enumsortorder values under MVCC catalog scan semantics. Restore
some of the previous text, with hopefully-correct adjustments for
the new state of play.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/c9e2e2db5c2090a880028fd8c1debff474640f50
Modified Files
--------------
src/backend/catalog/pg_enum.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)