On Tue, Sep 20, 2011 at 11:13:05AM -0400, Tom Lane wrote: > 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.
How about a per-table setting that tells autovacuum whether to do this? Come to think of it, all of per-FDW, per-remote and per-table settings would be handy, so people could express things like, "all CSV files except these three, all PostgreSQL connections on the 10.1.0.0/16 network, and these two tables in Oracle." Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers