aboutsummaryrefslogtreecommitdiff
path: root/src/backend/regex/regexec.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-15 16:18:34 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-15 16:19:01 -0500
commit4bfe68dfab009ce8fcaea79dc0832eadf3380051 (patch)
treea3cfddf505fa6b8136b2fc26324ee930bdb390e1 /src/backend/regex/regexec.c
parentedec8c8e00e3f2a9305ab92e2c81293457cf959a (diff)
downloadpostgresql-4bfe68dfab009ce8fcaea79dc0832eadf3380051.tar.gz
postgresql-4bfe68dfab009ce8fcaea79dc0832eadf3380051.zip
Run a portal's cleanup hook immediately when pushing it to FAILED state.
This extends the changes of commit 6252c4f9e201f619e5eebda12fa867acd4e4200e so that we run the cleanup hook earlier for failure cases as well as success cases. As before, the point is to avoid an assertion failure from an Assert I added in commit a874fe7b4c890d1fe3455215a83ca777867beadd, which was meant to check that no user-written code can be called during portal cleanup. This fixes a case reported by Pavan Deolasee in which the Assert could be triggered during backend exit (see the new regression test case), and also prevents the possibility that the cleanup hook is run after portions of the portal's state have already been recycled. That doesn't really matter in current usage, but it foreseeably could matter in the future. Back-patch to 9.1 where the Assert in question was added.
Diffstat (limited to 'src/backend/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions