| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marti Raudsepp <marti(at)juffo(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Collecting statistics on CSV file data |
| Date: | 2011-10-07 11:09:44 |
| Message-ID: | 4E8EDDF8.9080803@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I'm very sorry for the late reply.
(2011/09/21 10:00), Alvaro Herrera wrote:
> Excerpts from David Fetter's message of mar sep 20 21:22:32 -0300 2011:
>> On Tue, Sep 20, 2011 at 11:13:05AM -0400, Tom Lane wrote:
>
>>> 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?
>
> Seems reasonable. Have autovacuum assume that foreign tables are not to
> be analyzed, unless some reloption is set.
Thank you for the comments. I'd like to leave that feature for future work.
(But this is BTW. I'm interested in developing CREATE FOREIGN INDEX.
I've examined whether there are discussions about the design and
implementation of it in the archive, but could not find information. If
you know anything, please tell me.)
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-10-07 12:39:57 | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |
| Previous Message | Heikki Linnakangas | 2011-10-07 10:31:30 | Re: Why does WAL_DEBUG macro need to be defined by default? |