Vacuum cancels autovacuum error message confusing?

All:

NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index
"pgbench_branches_pkey" for table "pgbench_branches"
NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index
"pgbench_tellers_pkey" for table "pgbench_tellers"
NOTICE:  ALTER TABLE / ADD PRIMARY KEY will create implicit index
"pgbench_accounts_pkey" for table "pgbench_accounts"

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?

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com