| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Create index on foreign table |
| Date: | 2012-03-19 05:35:49 |
| Message-ID: | 4F66C5B5.9030208@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2012/03/17 2:07), David Fetter wrote:
> On Fri, Mar 16, 2012 at 11:58:29AM +0200, Heikki Linnakangas wrote:
>> On 16.03.2012 10:44, Etsuro Fujita wrote:
>>> For a flat file, CREATE INDEX constructs
>>> an index in the same way as an index for a regular table.
>> For starters, how would you keep the index up-to-date when the flat
>> file is modified?
> One way is to poll the remote source for evidence of such changes
> during auto_vacuum or with similar daemon processes. Another is by
> waiting for a signal from an external source such as a NOTIFY. Which
> is more appropriate will again depend on circumstances.
I think that's a good idea. I'd like to work on it in the future.
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2012-03-19 08:59:11 | Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation) |
| Previous Message | Etsuro Fujita | 2012-03-19 05:34:01 | Re: Proposal: Create index on foreign table |