On Tue, Sep 7, 2010 at 11:41 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Oh, well you certainly didn't explain it well then.
>
> What I *think* you're saying is that the slave doesn't send per-commit
> messages, but instead processes the WAL as it's received and then sends
> a heres-where-I-am status message back upstream immediately before going
> to sleep waiting for the next chunk. That's fine as far as the protocol
> goes, but I'm not convinced that it really does all that much in terms
> of improving performance. You still have the problem that the master
> has to fsync its WAL before it can send it to the slave.
We have that problem in all of these proposals, don't we? We
certainly have no infrastructure to handle the slave getting ahead of
the master in the WAL stream.
> Also, the
> slave won't know whether it ought to fsync its own WAL before replying.
Right. And whether it ought to replay it before replying.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company