Josh Berkus <j...@agliodbs.com> writes:
> vacuum...ERROR: canceling autovacuum task
> CONTEXT: automatic analyze of table "bench.public.pgbench_accounts"
> ERROR: canceling autovacuum task
> CONTEXT: automatic analyze of table "bench.public.pgbench_accounts"
> done.
> What happened above is that the build of the new pgbench database
> triggered an autovacuum, and then pgbench called a manual vacuum,
> cancelling the autovacuum.
> However, the error message which autovacuum gives does not indicate that
> it was superceded by a manual vacuum, which could confuse users and make
> them think there's some kind of actual vacuum failure. Is it worth
> fixing the error message?
What's to fix? The autovacuum was in fact canceled. What would you
propose doing differently?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
