Hi Niranjan,
I'm sorry for this late reply.
On Tue, Feb 24, 2009 at 5:24 PM, K, Niranjan (NSN - IN/Bangalore)
<niranjan.k@nsn.com> wrote:
> Steps to re-produce the sync replication bug:
>
> - Setup the Primary server and standby server
> - Don't execute any transactions on the Primary server
> - Initiate a switchover by creating a finish.trigger on the Standby server
> - The standby server (the startup process) will terminate with SIGABRT signal and no connection to the Database will
bepossible after that.
The attached patch fixed the problem which you reported.
So, please try this updated patch.
The list of updates is:
* Fix the problem which SIGTERM may be unable to shut down the
startup process.
* Fix the problem which the standby server fails when the trigger
file is created just after replication starts. Reported by Niranjan.
* Rename the parameter to specify whether to enable WAL receiving
by the standby from "enable_replication" to "replication".
* Change postmaster to send the SIGHUP signal to also walreceiver.
http://wiki.postgresql.org/wiki/NTT%27s_Development_Projects#Version_History
As above, the parameter "enable_replication" was renamed,
so please change your test script which sets this parameter
before testing.
And, for your convenience, I also uploaded the source code
(HEAD) with this updated patch. If you find something odd
about Synch Rep, please report it.
http://senduit.com/d9a57f
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
