diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-02 15:31:14 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-06-02 15:31:14 -0400 |
| commit | 918eb0f34f2af3e0d2823a164d22b6906d46dfcd (patch) | |
| tree | 09fd57a20b0fa0de6d546263bf0a2dae04084ecb /src/backend/access/gist | |
| parent | 23138a5203fe14d6adf5019482f341ebfe2136ad (diff) | |
| download | postgresql-918eb0f34f2af3e0d2823a164d22b6906d46dfcd.tar.gz postgresql-918eb0f34f2af3e0d2823a164d22b6906d46dfcd.zip | |
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.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions