Fix Windows implementation of PGSemaphoreLock. The original coding failed to reset ImmediateInterruptOK before returning, which would potentially allow a subsequent query-cancel interrupt to be accepted at an unsafe point. This is a really nasty bug since it's so hard to predict the consequences, but they could be unpleasant.
Also, ensure that signal handlers are serviced before this function returns, even if the semaphore is already set. This should make the behavior more like Unix. Back-patch to all supported versions. Branch ------ REL8_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/fcc0ba313b41437b9efc01438f133feb484b2e93 Modified Files -------------- src/backend/port/win32_sema.c | 20 ++++++++++++-------- 1 files changed, 12 insertions(+), 8 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
