| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, "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 19:01:28 |
| Message-ID: | 9645.1255978888@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> writes:
> 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.
It will autoanalyze once a sufficient number of inserts have occurred.
The effect of a crash is just to reset the inserts-since-last-analyze
counters. You really haven't made the case why that's so awful that
we need to do things that are unpleasant along other dimensions in order
to avoid it. (The only ways of avoiding it that I can see would result
in very significant overhead added to the stats collection mechanism.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2009-10-19 19:09:45 | Re: autovacuum and immediate shutdown issues |
| Previous Message | Brad Nicholson | 2009-10-19 18:52:47 | Re: autovacuum and immediate shutdown issues |