From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Can you spot the difference? |
Date: | 2013-04-16 23:29:10 |
Message-ID: | 516DDEC6.8070000@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/16/2013 01:55 PM, Moshe Jacobson wrote:
> On Tue, Apr 16, 2013 at 3:29 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com
> <mailto:adrian(dot)klaver(at)gmail(dot)com>> wrote:
>
> Given that the copy is causing the 'problem', the question to ask
> is; did you run ANALYZE on the table once the data was copied in?
>
>
> I did not -- I expected the autovacuum daemon to do so. Why did it not?
> The database was created & restored days ago, and the autovacuum daemon
> is running with default settings.
http://www.postgresql.org/docs/9.2/static/routine-vacuuming.html
"
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.
>
> Thanks.
>
> --
> Moshe Jacobson
> Nead Werx, Inc. | Manager of Systems Engineering
> 2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
> moshe(at)neadwerx(dot)com <mailto:moshe(at)neadwerx(dot)com> | www.neadwerx.com
> <http://www.neadwerx.com/>
>
> "Quality is not an act, it is a habit." -- Aristotle
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-04-16 23:31:44 | Re: SQL keywords are suddenly case sensitive |
Previous Message | Adrian Klaver | 2013-04-16 23:26:40 | Re: JDBC driver versions |