| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: Synchronous Log Shipping Replication |
| Date: | 2008-09-09 13:16:14 |
| Message-ID: | 48C6771E.8030501@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Dimitri Fontaine wrote:
> It might just be I'm not understanding what it's all about, but it seems to me
> with WALSender process A will wait, whatever happens, either until the WAL is
> sent to slave or written to disk on the slave.
..and it will still has to wait until WAL is written to disk on the
local node, as we do now. These are two different things to wait for.
One is a network socket operation, the other is an fsync(). As these
don't work together too well (blocking), you better run that in two
different processes.
Regards
Markus Wanner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2008-09-09 13:32:42 | Re: Synchronous Log Shipping Replication |
| Previous Message | Martin Pihlak | 2008-09-09 13:11:58 | Re: reducing statistics write overhead |