>> ...
>
> 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.