webb sprague <wsprague@o1.com> writes:
> Unfortunately, the problem snow seems to happen when I vacuum-analyze
> after a big delete. Even if the vacuum takes more than 2 minutes (the
> amount of time between flushes that I set in postgresql.conf), the
> logs continue to grow.
I don't think there's any way around that at the moment :-(. The old
log segments cannot be deleted as long as they include information about
as-yet-uncommitted transactions, and the VACUUM is one big transaction.
It would theoretically be possible to delete old log segments from
before the last checkpoint (or better, next-to-last checkpoint) if
we were only concerned about using the logs for crash recovery.
I imagine Vadim will object to that, however, since he has in mind
using the logs for UNDOing aborted transactions sometime soon.
A more likely solution path will be to eliminate VACUUM or break it
into smaller transactions...
regards, tom lane
