Revision 1bdae16fca884a9190dc330790e7a63c04989fa3 authored by Alvaro Herrera on 01 July 2016, 17:53:46 UTC, committed by Alvaro Herrera on 01 July 2016, 17:53:46 UTC
There are two problems in the original coding: one is that if one walreceiver process exits, the ready_to_display flag remains set in shared memory, exposing the conninfo of the next walreceiver before obfuscating. Fix by having WalRcvDie reset the flag. Second, the sleep-and-retry behavior that waited until walreceiver had set ready_to_display wasn't liked; the preference is to have it return no data instead, so let's do that. Bugs in 9ed551e0a reported by Fujii Masao and Michël Paquier. Author: Michaël Paquier
1 parent 9e70398
Computing file changes ...
