| From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Postgresql-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Backing up the currently used wal segment |
| Date: | 2006-07-06 18:13:00 |
| Message-ID: | 44AD52AC.9060007@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure wrote:
> On 7/6/06, Florian G. Pflug <fgp(at)phlo(dot)org> wrote:
>> Hi
>>
>> I've implemented replication to a warm standby using wal
>> logshipping now. The only remaining problem is that there
>
> just how exactly does this work? are you constantly firing up the
> standby server?
Postgres on the standby server is running constantly. The restore_command
is a shell script that waits indefinitely if a wal is requested that doesn't
exist yet. A periodic cron-jobs (every minute) syncs the archived wals over
to the standby maschine, where they are eventually picked by the restore_command.
greetings, Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-07-06 18:20:31 | Re: How to hide NOTICE messages in psql.exe ? |
| Previous Message | Brennan, Sean (IMS) | 2006-07-06 18:06:46 | Delete cascade and trigger permissions? |