| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Collecting statistics on CSV file data |
| Date: | 2011-09-20 14:12:48 |
| Message-ID: | CABRT9RA0Xq+jaN115BBTotrBUgQY0k7bvQJSLWQd8Ug1ohUiwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Currently it looks like the only way to reset statistics is to tamper
with catalogs directly, or recreate the foreign table.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-09-20 14:13:41 | Re: Separating bgwriter and checkpointer |
| Previous Message | Alvaro Herrera | 2011-09-20 14:12:03 | Re: Is there really no interest in SQL Standard? |