Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Michael Paquier
On Sat, Jul 4, 2015 at 2:44 AM, Andres Freund wrote: > This subthread is getting absurd, stopping here. Yeah, I agree with Andres here, we are making a mountain of nothing (Frenglish?). I'll send to the other thread some additional ideas soon using a JSON structure. -- Michael -- Sent via pgsq

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Andres Freund
On 2015-07-03 10:27:05 -0700, Josh Berkus wrote: > On 07/03/2015 03:12 AM, Sawada Masahiko wrote: > > Thanks. So we can choice the next master server using by checking the > > progress of each server, if hot standby is enabled. > > And a such procedure is needed even today replication. > > > > I t

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Josh Berkus
On 07/03/2015 03:12 AM, Sawada Masahiko wrote: > Thanks. So we can choice the next master server using by checking the > progress of each server, if hot standby is enabled. > And a such procedure is needed even today replication. > > I think that the #2 problem which is Josh pointed out seems to b

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Andres Freund
On 2015-07-02 14:54:19 -0700, Josh Berkus wrote: > On 07/02/2015 12:44 PM, Andres Freund wrote: > > On 2015-07-02 11:50:44 -0700, Josh Berkus wrote: > >> So there's two parts to this: > >> > >> 1. I need to ensure that data is replicated to X places. > >> > >> 2. I need to *know* which places data

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Sawada Masahiko
On Fri, Jul 3, 2015 at 6:23 PM, Fujii Masao wrote: > On Fri, Jul 3, 2015 at 5:59 PM, Sawada Masahiko wrote: >> Yeah, quorum commit is helpful for minimizing data loss in comparison >> with today replication. >> But in this your case, how can we know which server we should use as >> the next maste

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Fujii Masao
On Fri, Jul 3, 2015 at 5:59 PM, Sawada Masahiko wrote: > On Fri, Jul 3, 2015 at 12:18 PM, Fujii Masao wrote: >> On Fri, Jul 3, 2015 at 6:54 AM, Josh Berkus wrote: >>> On 07/02/2015 12:44 PM, Andres Freund wrote: On 2015-07-02 11:50:44 -0700, Josh Berkus wrote: > So there's two parts to

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-03 Thread Sawada Masahiko
On Fri, Jul 3, 2015 at 12:18 PM, Fujii Masao wrote: > On Fri, Jul 3, 2015 at 6:54 AM, Josh Berkus wrote: >> On 07/02/2015 12:44 PM, Andres Freund wrote: >>> On 2015-07-02 11:50:44 -0700, Josh Berkus wrote: So there's two parts to this: 1. I need to ensure that data is replicated to

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-02 Thread Fujii Masao
On Fri, Jul 3, 2015 at 6:54 AM, Josh Berkus wrote: > On 07/02/2015 12:44 PM, Andres Freund wrote: >> On 2015-07-02 11:50:44 -0700, Josh Berkus wrote: >>> So there's two parts to this: >>> >>> 1. I need to ensure that data is replicated to X places. >>> >>> 2. I need to *know* which places data was

Re: [HACKERS] Synch failover WAS: Support for N synchronous standby servers - take 2

2015-07-02 Thread Josh Berkus
On 07/02/2015 12:44 PM, Andres Freund wrote: > On 2015-07-02 11:50:44 -0700, Josh Berkus wrote: >> So there's two parts to this: >> >> 1. I need to ensure that data is replicated to X places. >> >> 2. I need to *know* which places data was synchronously replicated to >> when the master goes down. >