Andres Freund <and...@2ndquadrant.com> writes: > I am pretty sure by now that the sane fix for this is to add a > SetLatch() call to RecoveryConflictInterrupt(). All the signal handlers > that deal with query cancelation et al. do so, so it seems right that > RecoveryConflictInterrupt() does so as well.
+1
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
