Re: Hot standby documentation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Markus Wanner <markus(at)bluegap(dot)ch>
Cc: Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hot standby documentation
Date: 2010-02-08 13:34:06
Message-ID: 201002081334.o18DY6v24223@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Markus Wanner wrote:
> Bruce,
>
> Bruce Momjian wrote:
> > Ah, I now realize it only mentions "warm" standby, not "hot", so I just
> > updated the documentation to reflect that; you can see it here:
>
> Maybe the table below also needs an update, because unlike "Warm Standby
> using PITR", a hot standby accepts read-only queries and can be
> configured to not loose data on master failure.

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". You
can see the result here:

http://momjian.us/tmp/pgsql/high-availability.html

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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tim Bunce 2010-02-08 13:44:16 Re: Add on_plperl_init and on_plperlu_init to plperl UPDATE 3 [PATCH]
Previous Message Alvaro Herrera 2010-02-08 13:23:11 Re: Largeobject Access Controls (r2460)