From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:09:45 |
Message-ID: | 1255979385.4316.67.camel@bnicholson-desktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2009-10-19 at 15:01 -0400, Tom Lane wrote:
> 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.)
What about the question that Scott and I both asked - what about query
plans. Will they be affected?
If so, you could have a table that does not get updated, that no longer
generates relevant query plans, and won't until manual intervention.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
From | Date | Subject | |
---|---|---|---|
Next Message | Brad Nicholson | 2009-10-19 19:14:25 | Re: autovacuum and immediate shutdown issues |
Previous Message | Tom Lane | 2009-10-19 19:01:28 | Re: autovacuum and immediate shutdown issues |