aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_target.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2001-09-26 21:09:27 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2001-09-26 21:09:27 +0000
commitd435592f33a6f323d94c9f33fe3bc964c033b6d6 (patch)
tree7044534a1d08330fa2ce4149ebafccc0a9fe2aa0 /src/backend/parser/parse_target.c
parent1481b3b28b4ff250bbe31da9628dafa2b7e6687a (diff)
downloadpostgresql-d435592f33a6f323d94c9f33fe3bc964c033b6d6.tar.gz
postgresql-d435592f33a6f323d94c9f33fe3bc964c033b6d6.zip
Repair oversight in recent changes to index-creation: tuple time qual
check *can* return HEAPTUPLE_INSERT_IN_PROGRESS or HEAPTUPLE_DELETE_IN_PROGRESS, even though we have ShareLock on the relation. To wit, this can happen if the tuple was inserted/deleted by our own transaction. Per report from Justin Clift 9/23.
Diffstat (limited to 'src/backend/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions