From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Issues with two-server Synch Rep |
Date: | 2010-10-13 15:08:14 |
Message-ID: | 1286982494.1709.2425.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2010-10-11 at 11:07 -0700, Josh Berkus wrote:
> Absolutely. For a synch standby, you can't tolerate any standby delay
> at all. This means that anywhere from 1/4 to 3/4 of queries on the
> standby would be cancelled on any high-traffic OLTP server. Hence,
> "useless".
Don't agree with your numbers there and you seem to be assuming no
workarounds would be in use. A different discussion, I think.
> Interaction? My opinion is that the two are completely incompatible.
> You can't have synch rep and also have standby_delay > 0.
I would agree that adding an "apply" mode only makes sense when we have
master feedback to ensure that standby delay is minimised. But that's
not the only use case for sync rep and it doesn't actually help that
much.
Adding the feedback channel looks trivial to me, once we've got the main
sync rep patch in. I'll handle that.
For this reason, I've removed the "apply" mode from my patch, for now. I
want to get the simplest possible patch agreed and then add things
later.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-13 15:12:55 | Re: Extensions, this time with a patch |
Previous Message | Andrew Dunstan | 2010-10-13 14:59:18 | Re: SQL command to edit postgresql.conf, with comments |