Re: WIP: Collecting statistics on CSV file data - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: WIP: Collecting statistics on CSV file data
Date
Msg-id CABRT9RA0Xq+jaN115BBTotrBUgQY0k7bvQJSLWQd8Ug1ohUiwg@mail.gmail.com
Whole thread Raw
In response to WIP: Collecting statistics on CSV file data  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: WIP: Collecting statistics on CSV file data
Re: WIP: Collecting statistics on CSV file data
List pgsql-hackers
2011/9/12 Etsuro Fujita <fujita.etsuro@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.

Currently it looks like the only way to reset statistics is to tamper
with catalogs directly, or recreate the foreign table.

Regards,
Marti


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Is there really no interest in SQL Standard?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Separating bgwriter and checkpointer