| From: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | AgentM <agentm(at)themactionfaction(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication |
| Date: | 2006-08-21 19:17:08 |
| Message-ID: | 44EA06B4.7030902@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Davis wrote:
> Synchronous replication (to me) means that the data has been written to
> permanent storage on all masters and all slaves before any master or
> slave reports a successful COMMIT. Are you suggesting that you ship the
> WAL over the network, wait for it to be written to the slave, and then
> report a successful commit?
I'm not suggesting doing replication like that. But I think that's what
people mean when they propose that "multi-master synchronous replication
would be fairly trivial to implement with 2PC and wal-shipping".
This is more or less trivial to implement, yes. But it won't scale.
Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-08-21 19:21:37 | Re: Replication |
| Previous Message | AgentM | 2006-08-21 19:14:10 | Re: Replication |