Clean up after erroneous SELECT FOR UPDATE/SHARE on a sequence.
My previous commit disallowed this operation, but did nothing about
cleaning up the damage if one had already been done. With the operation
disallowed, it's okay to just forcibly clear xmax in a sequence's tuple,
since any value seen there could not represent a live transaction's lock.
So, any sequence-specific operation will repair the problem automatically,
whether or not the user has already seen "could not access status of
transaction" failures.
Branch
------
REL8_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/918eb0f34f2af3e0d2823a164d22b6906d46dfcd
Modified Files
--------------
src/backend/commands/sequence.c | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
