From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Hot standby documentation |
Date: | 2010-02-05 23:55:39 |
Message-ID: | 201002052355.o15NtdK20314@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua Tolley wrote:
-- Start of PGP signed section.
> 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
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:
http://momjian.us/tmp/pgsql/high-availability.html
Warm and Hot Standby Using Point-In-Time Recovery (PITR)
Do we want to call the feature "hot standby"? Is a read-only standby a
"standby" or a "slave"?
--
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. +
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-02-06 00:24:57 | Re: WIP patch for system-catalog vacuuming via a relation map |
Previous Message | Marko Kreen | 2010-02-05 23:47:19 | Re: Confusion over Python drivers |