From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Can you spot the difference? |
Date: | 2013-04-17 14:49:15 |
Message-ID: | CAJ4CxLk5gvkVYT1c0xGn-Qh-QXNsDUZKXW8ZssOZsxuLfNUz8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Apr 16, 2013 at 7:29 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>wrote:
> "
> The autovacuum daemon, if enabled, will automatically issue ANALYZE
> commands whenever the content of a table has changed sufficiently. However,
> administrators might prefer to rely on manually-scheduled ANALYZE
> operations, particularly if it is known that update activity on a table
> will not affect the statistics of "interesting" columns. The daemon
> schedules ANALYZE strictly as a function of the number of rows inserted or
> updated; it has no knowledge of whether that will lead to meaningful
> statistical changes.
> "
>
> So at a guess there has not been enough churn on the table.
>
So pg_restore's COPY would not trigger the ANALYZE? That seems wrong.
--
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
moshe(at)neadwerx(dot)com | www.neadwerx.com
"Quality is not an act, it is a habit." -- Aristotle
From | Date | Subject | |
---|---|---|---|
Next Message | Dale Fukami | 2013-04-17 14:53:44 | Re: Mysterious table that exists but doesn't exist |
Previous Message | Philipp Kraus | 2013-04-17 14:44:17 | Re: dataset lock |