[COMMITTERS] pgsql: Fix Windows implementation of PGSemaphoreLock.

2012-05-10 Thread Tom Lane
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,

[COMMITTERS] pgsql: Fix Windows implementation of PGSemaphoreLock.

2012-05-10 Thread Tom Lane
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,

[COMMITTERS] pgsql: Fix Windows implementation of PGSemaphoreLock.

2012-05-10 Thread Tom Lane
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,

[COMMITTERS] pgsql: Fix Windows implementation of PGSemaphoreLock.

2012-05-10 Thread Tom Lane
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,

[COMMITTERS] pgsql: Fix Windows implementation of PGSemaphoreLock.

2012-05-10 Thread Tom Lane
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,