From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Hot standby documentation |
Date: | 2010-01-13 18:01:51 |
Message-ID: | 1263405711.26654.11257.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2010-01-07 at 18:34 +0900, Fujii Masao wrote:
> On Thu, Jan 7, 2010 at 6:09 PM, Joshua Tolley <eggyknap(at)gmail(dot)com> wrote:
> > Having concluded I really need to start playing with hot standby, I started
> > looking for documentation on the subject. I found what I was looking for; I
> > also found this page[1], which, it seems, ought to mention hot standby.
> > Comments?
> >
> > [1] http://developer.postgresql.org/pgdocs/postgres/high-availability.html
>
> +1
>
> At least, it should be mentioned that the slave can answer
> read-only queries in "Warm Standby Using Point-In-Time Recovery".
> And so "Table 25-1" should be changed.
OK, will add.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2010-01-13 18:08:48 | Re: plpython3 |
Previous Message | Peter Eisentraut | 2010-01-13 17:53:11 | Re: plpython3 |