From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Samba <saasira(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Statistics about Streaming Replication deployments in production |
Date: | 2011-07-31 17:15:36 |
Message-ID: | CA+U5nMK586=F-Cidnsxnd0x5MSzZTRfR7FLG-MU=PDz0ZEqtFw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jul 28, 2011 at 12:03 PM, Samba <saasira(at)gmail(dot)com> wrote:
> I think one year is sufficient time for any product/feature to be thoroughly
> tested for all its strengths and weaknesses; so would it be too much to ask
> the vast postgres customer base about their experiences with streaming
> replication, the good, the bad; and perhaps the best and the ugly too? It
> would be great if customers can give their identity (employer info) but not
> necessary though.
Maybe its not clear in the documentation but the streaming replication
feature isn't just one year old.
The core parts of it are actually 7 years old, and they are definitely
battle tested. The slightly newer parts changed the transport logic to
stream rather than use file-by-file.
The features relevant here are Point in Time Recovery (8.0), Warm
Standby (8.2), pg_standby (8.3), Bgwriter during recovery (8.4)
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Veyron | 2011-07-31 17:29:10 | User Interface [was : eval function] |
Previous Message | John R Pierce | 2011-07-31 17:10:54 | Re: eval function |