From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
---|---|
To: | Marti Raudsepp <marti(at)juffo(dot)org> |
Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: Collecting statistics on CSV file data |
Date: | 2011-09-20 15:24:26 |
Message-ID: | 4E78B02A.6060605@timbira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 20-09-2011 11:12, Marti Raudsepp wrote:
> 2011/9/12 Etsuro Fujita<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>:
>> This is called when ANALYZE command is executed. (ANALYZE
>> command should be executed because autovacuum does not analyze foreign
>> tables.)
>
> This is a good idea.
>
> However, if adding these statistics requires an explicit ANALYZE
> command, then we should also have a command for resetting the
> collected statistics -- to get it back into the un-analyzed state.
>
Why would you want this? If the stats aren't up to date, run ANALYZE
periodically. Remember that it is part of the DBA maintenance tasks [1].
[1] http://www.postgresql.org/docs/current/static/maintenance.html
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-09-20 15:42:21 | Re: File not found error on creating collation |
Previous Message | Tom Lane | 2011-09-20 15:13:05 | Re: WIP: Collecting statistics on CSV file data |