Re: FOREIGN TABLE doc fix

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FOREIGN TABLE doc fix
Date: 2011-06-14 06:58:55
Message-ID: BANLkTinup2F0eJ8n7ZoQEvzxfgf8h6R50A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 13, 2011 at 8:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Page <dpage(at)pgadmin(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2011-06-14 07:45:32 Re: 9.1 beta1 error
Previous Message Jun Ishiduka 2011-06-14 06:52:12 Re: Online base backup from the hot-standby