]> granicus.if.org Git - postgresql/commit
Partially restore comments discussing enum renumbering hazards.
authorRobert Haas <rhaas@postgresql.org>
Wed, 28 Aug 2013 17:21:08 +0000 (13:21 -0400)
committerRobert Haas <rhaas@postgresql.org>
Wed, 28 Aug 2013 17:21:08 +0000 (13:21 -0400)
commitc9e2e2db5c2090a880028fd8c1debff474640f50
tree060e23ef624dbd7a9180693cc38bbd8f2fd71668
parentda85fb4747ac0b7f787ef7a402adea2747e32d8e
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.
src/backend/catalog/pg_enum.c