As Alvaro already mentioned this is fixed in 8.1 because it was
integrated into the backend and benifits from the logging features that
backend already has developed.
As for the 7.4.x & 8.0.x versions of contrib autovacuum, I don't think
there are any plans for improving it. Also, added it to
Ameet Kini wrote:
>
> Any plans of incorporating it into a future release? How do people
> currently deal with this problem? I wonder if this is fixed in the
> pg_autovacuum distributed with v8.1
8.1 does not have this problem, because autovacuum got integrated into
the server proper and no longe
Most people running Linux would add it to their logrotate.conf or other log
management methods.
On Mon, 12 Dec 2005, Ameet Kini wrote:
Any plans of incorporating it into a future release? How do people
currently deal with this problem? I wonder if this is fixed in the
pg_autovacuum distribut
Any plans of incorporating it into a future release? How do people
currently deal with this problem? I wonder if this is fixed in the
pg_autovacuum distributed with v8.1
On Sun, 11 Dec 2005, Matthew T. O'Connor wrote:
> Unfortunately, you are correct, there is no way to tell
> contrib/autovacu
Unfortunately, you are correct, there is no way to tell
contrib/autovacuum to rotate it's logs.
Ameet Kini wrote:
Hello,
I'm using postgresql 8.0 and am using contrib/pg_autovacuum. Is there a
way to tell pg_autovacuum to rotate the log that it generates after
it reaches a particular size? Fro
Hello,
I'm using postgresql 8.0 and am using contrib/pg_autovacuum. Is there a
way to tell pg_autovacuum to rotate the log that it generates after
it reaches a particular size? From the set of command line options, it
seems that its only possible to specify the location of the logfile (via
the -
