Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-30 Thread Sawada Masahiko
On Wed, Aug 28, 2013 at 10:59 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Tue, Aug 27, 2013 at 4:51 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Aug 25, 2013 at 3:21 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-28 Thread Amit Kapila
On Tue, Aug 27, 2013 at 4:51 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sun, Aug 25, 2013 at 3:21 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-27 Thread Sawada Masahiko
On Sun, Aug 25, 2013 at 3:21 PM, Amit Kapila amit.kapil...@gmail.com wrote: On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus j...@agliodbs.com wrote: On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-27 Thread Kevin Grittner
Amit Kapila amit.kapil...@gmail.com wrote: What is happening here is that incase of '*' as priority of both are same, system will choose whichever comes in list of registered standby's first (list is maintained in structure WalSndCtl).  Each standby is registered with WalSndCtl when a new

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-27 Thread Sawada Masahiko
On Wed, Aug 28, 2013 at 5:51 AM, Kevin Grittner kgri...@ymail.com wrote: Amit Kapila amit.kapil...@gmail.com wrote: What is happening here is that incase of '*' as priority of both are same, system will choose whichever comes in list of registered standby's first (list is maintained in

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-25 Thread Amit Kapila
On Sat, Aug 24, 2013 at 2:46 PM, Sawada Masahiko sawada.m...@gmail.com wrote: On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus j...@agliodbs.com wrote: On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those priority is clear. So I think that re-taking over is correct behaviour. OHOT,

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-24 Thread Sawada Masahiko
On Sat, Aug 24, 2013 at 3:14 AM, Josh Berkus j...@agliodbs.com wrote: On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those priority is clear. So I think that re-taking over is correct behaviour. OHOT, in case (b), even if AAA and BBB are set same priority, AAA server steals SYNC

[HACKERS] Behaviour of take over the synchronous replication

2013-08-23 Thread Sawada Masahiko
Hi all, I understand that setting synchronous_standby_name to '*' means that all priority of standby server are same. and the standby server, which connected to the master server at first, become SYNC standby, another server become ASYNC standby as potential server. So, how to set the priority

Re: [HACKERS] Behaviour of take over the synchronous replication

2013-08-23 Thread Josh Berkus
On 08/23/2013 12:42 AM, Sawada Masahiko wrote: in case (a), those priority is clear. So I think that re-taking over is correct behaviour. OHOT, in case (b), even if AAA and BBB are set same priority, AAA server steals SYNC replication. I think it is better that BBB server continue behaviour