| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Hot standby documentation |
| Date: | 2010-01-07 09:34:48 |
| Message-ID: | 3f0b79eb1001070134v702f9341k5217481e33afa2b8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-01-07 09:50:38 | Re: Testing with concurrent sessions |
| Previous Message | Albe Laurenz | 2010-01-07 09:33:07 | Re: true serializability and predicate locking |