| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-cluster-hackers(at)postgresql(dot)org |
| Subject: | Re: Function scan push-down using SQL/MED syntax |
| Date: | 2010-03-04 18:08:36 |
| Message-ID: | 4B8FF724.4070102@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cluster-hackers |
On 3/3/10 8:52 PM, Takahiro Itagaki wrote:
> The current design is very similar to "Executor node hook".
> ExecXxxForeignScan() almost pass-through the processing to each FDW
> routine. SQL-based FDWs can push-down the conditions to their foreign
> servers. Also, plain data FDWs (including CSV-FDW) can give over
> the filtering to the default executor.
It would be really good to have access to the scan criteria as text, a
hash, or other generally manipulable data structures, as well, for
foreign data which is not SQL-based.
Finally, if you are making the scan more visible, a nice side effect of
this would be the ability to log all the scan criteria on a particular
table (whether its an FDW or not); it would help a lot with indexing.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2010-03-05 15:51:16 | Re: Function scan push-down using SQL/MED syntax |
| Previous Message | Takahiro Itagaki | 2010-03-04 04:52:19 | Function scan push-down using SQL/MED syntax |