From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Hot standby documentation |
Date: | 2010-02-09 00:45:12 |
Message-ID: | 3f0b79eb1002081645p2a714e6ck703c61a626b08615@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 8, 2010 at 10:34 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Ahh, good point. I had not considered the table would change. What I
> did was to mark "Slaves accept read-only queries" as "Hot only".
Can the "warm standby" still reside in v9.0? If not, the mark of
"Hot only" seems odd for me.
> I did not change "Master failure will never lose data" because the 9.0
> streaming implementation is not sychronous (see wal_sender_delay in
> postgresql.conf), and I don't think even setting that to zero makes the
> operation synchronous. I think we will have to wait for PG 9.1 for
> _synchronous_ streaming replication.
You are right.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-02-09 01:07:00 | buildfarm breakage |
Previous Message | Tom Lane | 2010-02-09 00:35:43 | Re: Order of operations in lazy_vacuum_rel |