From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | postgres(at)pivert(dot)org |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Switch log (WAL) |
Date: | 2006-02-13 17:43:50 |
Message-ID: | 20060213174350.GA57845@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, Feb 12, 2006 at 11:47:11AM +0100, postgres(at)pivert(dot)org wrote:
> Hello,
>
> I'm new to the list, and I'm intereted in PostgreSQL replication (using WAL)
> As I didn't find any script to do that, I make mine, that seems to work.
>
> However, I wonder how can I "switch WAL logs", in order to have the standby
> database not too much late.
> The database actually generates few logs, and I would like one WAL to be
> generated once per hour.
>
> How Can I do that ?
You can't. What you can do is copy the most recently touched log file as
often as you'd like. That will limit your data loss should you need to
fail-over.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-02-13 17:46:31 | Re: vacuumdb |
Previous Message | Tom Lane | 2006-02-13 17:25:33 | Re: Lost tables in Postgres 7.1 |