| From: | Ian Lea <ian(dot)lea(at)gmail(dot)com> |
|---|---|
| To: | Khusro Jaleel <mailing-lists(at)kerneljack(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Backing up a replication set every 30 mins |
| Date: | 2012-02-15 16:19:26 |
| Message-ID: | CAEY5pxXvtst2HfY40mwh6u0FkhE=MTmBOBbtkkEkzRCgVJ6vAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>> ...
>
> That's exactly what I was trying to accomplish, however I tried to do a base
> backup every day and have archives during the day. This worked fine in
> testing, however when I set it up and attached the Java front-ends to the
> DB, there were *so* many archive files written to disk that the "rotate" job
> that runs every morning to do a new base backup failed. It failed because
> there were thousands upon thousands of archive files in the archive dir and
> it couldn't delete them. Why this happened I am not sure, I thought setting
> archive_timeout = 30 would only create 1 archive file every 30 minutes, but
> I was wrong.
If you've got archive_timeout = 30 that means 30 seconds, not 30 minutes.
--
Ian.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-02-15 16:21:58 | Re: Backing up a replication set every 30 mins |
| Previous Message | Khusro Jaleel | 2012-02-15 16:05:32 | Re: Backing up a replication set every 30 mins |