"Josh Berkus" <josh@agliodbs.com> writes:
> Actually, it's apparently a real problem, because the function never
> completes. Each cycle of "recycling transaction logs" takes longer
> and longer, and eventually locks up completely.
> What the function is doing is a succession of data cleanup procedures,
> updating the same table about 50 times. I will be very thankful for
> the day when I can commit within a procedure.
I think you are barking up the wrong tree.
The messages you show are perfectly normal operation, and prove nothing
much except that you pumped a lot of database updates through the
system. I think there's something wrong with your data transformation
application logic; or perhaps you are pumping so many updates through
your tables that you need some intermediate VACUUMs to get rid of
dead tuples. But messing with the WAL log parameters isn't going to
do a darn thing for you ... IMHO anyway.
regards, tom lane