| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Vacuum cancels autovacuum error message confusing? |
| Date: | 2010-04-21 01:13:09 |
| Message-ID: | 10383.1271812389@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-04-21 01:40:09 | Re: [HACKERS] Streaming replication document improvements |
| Previous Message | Tom Lane | 2010-04-21 01:03:53 | Re: Move tablespace |