Re: foreign data wrappers

Thanks for the slides! As what's mentioned on one of the slides, the datasource of FDW can be virtually everything.

So if there were a FDW for flickr API, the examples will be something like:

1) CREATE FOREIGN TABLE flickr_table (photo_id INT, ownerid INT, photo BLOB, text TEXT) SERVER flick_fdw OPTIONS (api_key 'AAAA');
p.s. the text field is used as the keyword for free text search.

when query from the table:
2) SELECT photo FROM flickr_table WHERE text = 'panda' LIMIT 0, 10;

This will return top ten photos relevant to 'panda'. Is my understanding correct?

I've briefly gone through the slides. Regarding the 6 callbacks, is that correct to say that a full table scan will always be performed irregardless of the sql statement,
the FDW is blind to the sql query performed, right?

And can anyone help explain what a planner is? What does this "provide cost estimates to planner" mean? Thanks!

Hi Shiv, I am also from National University of Singapore!

cheers,
ZY

On 25-Mar-2011, at 8:53 AM, Shiv wrote:

> Thank you for the slides. And yes FDW seems like a good project to get involved in especially if one (and by one I mean me) is knew to the Postgres codebase.
> Regards,
> Shiv
>
>
> On Fri, Mar 25, 2011 at 4:59 AM, Selena Deckelmann <selena(at)chesnok(dot)com> wrote:
> And, Andrew's slides from his talk today are now available:
> http://people.planetpostgresql.org/andrew/uploads/fdw2.pdf
>
> We really think the FDW projects would be great ones for GSoC. I know
> we said that already. :)
>
> -selena
>
> --
> Sent via pgsql-students mailing list (pgsql-students(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-students
>