Re: FOREIGN TABLE doc fix

On Mon, Jun 13, 2011 at 8:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dave Page <dpage@pgadmin.org> writes:
>> I've already implemented some simple qual pushdown in the redis FDW,
>> and am planning to do something similar for MySQL - however I won't be
>> surprised if I have to rewrite redisGetQual in
>> https://github.com/dpage/redis_fdw/blob/master/redis_fdw.c for
>> example.
>
> OK, *now* we're on the same page.  This sort of experimentation is
> exactly what I'm talking about: we'll certainly want to rewrite the code
> once we have better infrastructure, but it's necessary to write some
> throwaway code while we're learning what infrastructure FDWs want.
>
> (I find it a bit weird btw that you seem to be doing that at execution
> time not plan time...)

That's largely because as we discussed a while back
(http://archives.postgresql.org/pgsql-hackers/2011-04/msg00084.php),
persisting data from plan time to scan time isn't exactly clean.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company