Re: IMPORT FOREIGN SCHEMA return create foreign table commands are those further filtered in LIMIT and EXCEPT cases?

From: "Paragon Corporation" <lr(at)pcorp(dot)us>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: IMPORT FOREIGN SCHEMA return create foreign table commands are those further filtered in LIMIT and EXCEPT cases?
Date: 2015-12-31 21:48:00
Message-ID: 000a01d14414$eb3c3040$c1b490c0$@pcorp.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Paragon Corporation" <lr(at)pcorp(dot)us> writes:
>> So I am guessing you guys are filtering the list so that it works for
>> all FDWs even if the FDW author doesn't directly handle LIMIT / EXCEPT
clause?

> Yes. The FDW author is not expected to implement those clauses; where do
you see documentation saying otherwise?

> regards, tom lane

I didn't. I was copying the postgres_fdw and noticed it implemented them
directly.

Is there an issue with handling it ahead of time? In the case of ogr_fdw,
there is an extra call after getting list of tables to get the data
structure for a specific table,
So I thought implementing it directly would save some cycles, especially
since some data sources require inspection of the data to infer the
structure so could be very expensive.

Thanks,
Regina

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2015-12-31 21:49:27 Re: tracking owner of extension-managed objects
Previous Message Bruce Momjian 2015-12-31 21:43:38 Re: CurrentExtensionObject was Re: dynloader.h missing in prebuilt package for Windows?