Marti Raudsepp <ma...@juffo.org> writes:
> 2011/9/12 Etsuro Fujita <fujita.ets...@lab.ntt.co.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.
Uh, why? There is no UNANALYZE operation for ordinary tables, and
I've never heard anyone ask for one.
If you're desperate you could manually delete the relevant rows in
pg_statistic, a solution that would presumably work for foreign tables
too.
Probably a more interesting question is why we wouldn't change
autovacuum so that it calls this automatically for foreign tables.
(Note: I'm unconvinced that there's a use-case for this in the case of
"real" foreign tables on a remote server --- it seems likely that the
wrapper ought to ask the remote server for its current stats, instead.
But it's clearly useful for non-server-backed sources such as file_fdw.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
