| From: | Florian Pflug <fgp(dot)phlo(dot)org(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backup history file should be replicated in Streaming Replication? |
| Date: | 2009-12-18 17:22:34 |
| Message-ID: | 4B2BBA5A.9040703@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.12.09 17:05 , Robert Haas wrote:
> On Fri, Dec 18, 2009 at 11:03 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Or some way for to register the standby with the master so that
>> the master knows it's out there, and still needs the logs, even when
>> it's not connected.
>
> That is the real answer, I think.
It'd prefer if the slave could automatically fetch a new base backup if
it falls behind too far to catch up with the available logs. That way,
old logs don't start piling up on the server if a slave goes offline for
a long time.
The slave could for example run a configurable shell script in that
case, for example. You could then use that to rsync the data directory
from the server (after a pg_start_backup() of course).
best regards,
Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-18 17:29:45 | Re: Backup history file should be replicated in Streaming Replication? |
| Previous Message | Guillaume Lelarge | 2009-12-18 17:20:39 | Re: Time to run initdb is mostly figure-out-the-timezone work |