| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Phil Sorber <phil(at)omniti(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Teaching pg_receivexlog to follow timeline switches |
| Date: | 2013-01-22 13:10:17 |
| Message-ID: | 50FE8FB9.3020006@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.01.2013 15:02, Dimitri Fontaine wrote:
> Phil Sorber<phil(at)omniti(dot)com> writes:
>> What do you think about the idea of a full WAL proxy? Probably not for
>> 9.3 at this point though.
>
> I was thinking that a WAL proxy nowadays is called a cascading standby
> with local archiving enabled. I'm not sure why you would want to trust
> your archiving and WAL relaying to another piece of software…
You might not want to keep a copy of the whole data directory around, as
you have to in a cascading standby. I can see value in a separate WAL
proxy software, especially if it's integrated into a larger backup
manager program like barman or wal-e.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-01-22 13:15:28 | Re: CF3+4 (was Re: Parallel query execution) |
| Previous Message | Dimitri Fontaine | 2013-01-22 13:02:53 | Re: Teaching pg_receivexlog to follow timeline switches |