| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, AgentM <agentm(at)themactionfaction(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication |
| Date: | 2006-08-21 17:52:47 |
| Message-ID: | 20060821175246.GA11151@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Markus Schiltknecht wrote:
> Jeff Davis wrote:
> > How does WAL shipping help synchronous replication?
>
> The WAL is written _before_ commit, logging all the changes the
> transaction wants to write to the disk. This makes it look very similar
> to what is needed for synchronous replication.
>
> Instead of waiting for confirmation from the disk, that your WAL has
> been written, you would have to wait from the network to confirm that
> the changes have been delivered via the network.
But the confirmation that needs to come is that the WAL changes have
been applied (fsync'ed), so the performance will be terrible. So bad,
that I don't think anyone will want to use such a replication system ...
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-08-21 17:56:12 | Re: Altering view ownership doesn't work ... |
| Previous Message | Bruce Momjian | 2006-08-21 17:52:26 | Re: ISBN/ISSN/ISMN/EAN13 module |