Re: Synch Rep v5 - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Synch Rep v5
Date
Msg-id 1231594573.18005.665.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Synch Rep v5  ("Fujii Masao" <masao.fujii@gmail.com>)
Responses Re: Synch Rep v5  ("Fujii Masao" <masao.fujii@gmail.com>)
List pgsql-hackers
On Sat, 2009-01-10 at 19:16 +0900, Fujii Masao wrote:

> I attached the updated version of Synch Rep patch (v5) on wiki.
> The description of "User Overview" is also already updated.
> http://wiki.postgresql.org/wiki/NTT%27s_Development_Projects#Synch_Rep

Looks good on initial read of Wiki. Few minor comments:

The advantage of doing things this way is that the base backup can take
place any way the user chooses, so potentially much faster than using a
single session.

I notice we use the same settings for keepalives. We may need that to be
a second set of parameters.

Progress reporting will be easier with HS, so you are right to leave
that alone.

Don't understand: "Completely automated catching up; User has to carry
out some procedure manually for making the standby catch up."

Multiple standby is still possible, but just using old file based
mechanisms. We would need to be careful about use of %R in that case.

I believe the max delay is 2* wal_sender_delay.

I like the way recovery_trigger_file avoids changing pg_standby, but I
guess we still need to plug that gap also one day. But does patch 10
also have the other mechanism?

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: [BUGS] BUG #4516: FOUND variable does not work after RETURN QUERY
Next
From: Simon Riggs
Date:
Subject: Re: Synch Rep v5