| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | "K, Niranjan (NSN - IN/Bangalore)" <niranjan(dot)k(at)nsn(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, thoralf(dot)czichy(at)nsn(dot)com |
| Subject: | Re: Sync replication tests |
| Date: | 2009-02-24 16:46:24 |
| Message-ID: | 3f0b79eb0902240846r2f94ddfah30271435207080d6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Tue, Feb 24, 2009 at 5:24 PM, K, Niranjan (NSN - IN/Bangalore)
<niranjan(dot)k(at)nsn(dot)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 be possible after that.
Thanks for reporting the problem!
It's strange behavior. IIRC, any troubles didn't happen when I did the
same test.
I will test Synch Rep again and address the problem, but I'm away on business,
so please wait a week.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-02-24 17:36:11 | Re: Synchronous replication & Hot standby patches |
| Previous Message | Fujii Masao | 2009-02-24 15:51:16 | Re: Synchronous replication & Hot standby patches |