| From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org mailing list" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: autovacuum and immediate shutdown issues |
| Date: | 2009-10-19 18:52:47 |
| Message-ID: | 1255978367.4316.64.camel@bnicholson-desktop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2009-10-19 at 11:35 -0700, Christophe Pettus wrote:
> On Oct 19, 2009, at 11:26 AM, Scott Marlowe wrote:
> > That could be a pretty bad worst case scenario for certain types of
> > tables / usage patterns.
>
> Given that (presumably) the database server is not failing repeatedly
> without some kind of operator notification, isn't it at least somewhat
> reasonable to just make "start an vacuum upon recovery from an
> immediate shutdown" an operational procedure, rather than something PG
> does automatically?
>
It's not a vacuum you want, it's an analyze. Once the stats are back,
autovacuum will vacuum accordingly.
autoanalyze will automatically analyze new tables when they don't have
stats. It seems logical that it should handle this case where the table
also does not have stats.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-19 19:01:28 | Re: autovacuum and immediate shutdown issues |
| Previous Message | Christophe Pettus | 2009-10-19 18:35:31 | Re: autovacuum and immediate shutdown issues |