From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: sql/med review - problems with patching |
Date: | 2010-07-20 08:12:28 |
Message-ID: | AANLkTil4qdrAJbPToDzhfmtSOLVzUm9qVliFkqhgXDL-@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/7/14 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> please, can you refresh patch, please?
Updated patch attached. The latest version is always in the git repo.
http://repo.or.cz/w/pgsql-fdw.git (branch: fdw)
I'm developing the patch on postgres' git repo. So, regression test
for dblink might fail because of out-of-sync issue between cvs and git.
> When I looked to documentation I miss a some tutorial for foreign
> tables. There are only reference. I miss some paragraph where is
> cleanly and simple specified what is possible now and whot isn't
> possible. Enhancing of dblink isn't documented
Sure. I'll start to write documentation when we agree the design of FDW.
> In function pgIterate(ForeignScanState *scanstate) you are iterare
> via pg result. I am thinking so using a cursor and fetching multiple
> rows should be preferable.
Sure, but I'm thinking that it will be improved after libpq supports
protocol-level cursor. The libpq improvement will be applied
much more applications including postgresql_fdw.
--
Itagaki Takahiro
Attachment | Content-Type | Size |
---|---|---|
fdw_20100720.tar.gz | application/x-gzip | 92.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2010-07-20 09:09:06 | Re: Incorrect FTS result with GIN index |
Previous Message | Itagaki Takahiro | 2010-07-20 07:50:14 | Re: (9.1) btree_gist support for searching on "not equals" |