Re: FDW for PostgreSQL

Поиск
Список
Период
Сортировка
От Shigeru Hanada
Тема Re: FDW for PostgreSQL
Дата
Msg-id CAEZqfEfgHGAD9iVQiTWtrazrV31Ro=LioLPGrpUXN+L+0gUmyg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: FDW for PostgreSQL  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Ответы Re: FDW for PostgreSQL  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Список pgsql-hackers
Дерево обсуждения
Hi Kaigai-san,

Sorry for delayed response.   I updated the patch, although I didn't change any about timing issue you and Fujita-san concern.

1) add some FDW options for cost estimation.  Default behavior is not changed. 
2) get rid of array of libpq option names, similary to recent change of dblink
3) enhance document, especially remote query optimization
4) rename to postgres_fdw, to avoid naming conflict with the validator which exists in core
5) cope with changes about error context handling

On Tue, Nov 6, 2012 at 7:36 PM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote:
Isn't it possible to pick-up only columns to be used in targetlist or
local qualifiers,
without modification of baserestrictinfo?

IMO, it's possible.  postgres_fdw doesn't modify baserestrictinfo at all; it just create two new lists which exclusively point RestrictInfo elements in baserestrictinfo.  Pulling vars up from conditions which can't be pushed down would gives us list of  necessary columns.  Am I missing something?

--
Shigeru HANADA
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Switching timeline over streaming replication
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [v9.3] Extra Daemons (Re: elegant and effective way for running jobs inside a database)