| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First steps with 8.3 and autovacuum launcher |
| Date: | 2007-10-10 09:04:34 |
| Message-ID: | 470C95A2.6060708@gmx.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> OK, I've got this working now. It successfully handles this test case,
> which trips up on an auto ANALYZE every time I run it.
...
> I notice when we cancel an AV worker it always says "cancelling
> autovacuum of table", even when its just an ANALYZE. Wasn't important
> before but now looks a little strange.
...
> Any other input anyone?
What about VACUUM (not just ANALYZE)? The starter of the thread
"Possible bugreport 8.3 beta1 on Win32: Looking like a deadlock with
AutoVacuum" complained about vacuum, not analyze.
It is just as Tom said earlier: it will be before end of beta that
people will complain about more than just restoring dumps. ;-)
So does this approach work for both analyze as well as vacuum?
Best Regards
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-10-10 09:19:30 | Re: quote_literal with NULL |
| Previous Message | Dave Page | 2007-10-10 08:51:33 | Re: Locale + encoding combinations |