Re: SQL/MED estimated time of arrival?

Поиск
Список
Период
Сортировка
От Itagaki Takahiro
Тема Re: SQL/MED estimated time of arrival?
Дата
Msg-id AANLkTin4Qb_iYmBiQD1DrmQw6G_hHqWXRj04bo-0QYU-@mail.gmail.com
обсуждение исходный текст
Ответ на Re: SQL/MED estimated time of arrival?  (Shigeru HANADA <hanada@metrosystems.co.jp>)
Ответы Re: SQL/MED estimated time of arrival?  (Shigeru HANADA <hanada@metrosystems.co.jp>)
Re: SQL/MED estimated time of arrival?  (Shigeru HANADA <hanada@metrosystems.co.jp>)
Список pgsql-hackers
On Fri, Nov 5, 2010 at 4:00 PM, Shigeru HANADA
<hanada@metrosystems.co.jp> wrote:
>> > * am_beginscan()        -> first call of FdwRoutine.Iterate()?
>> It might be good to have a separated "beginscan" method if we use
>> asynchronous scans in multiple foreign servers in one query
>
> You mean that separated beginscan (FdwRoutine.BeginScan?) starts
> asynchronous query and returns immediately, and FdwRoutine.Iterate
> returns result of that query?

Yes. Each BeginScan() in the executor node tree will be called at
the beginning of executor's run. The callback should not block
the caller. OTOH, Iterate() are called at the first time tuples
in the node are required.

PL/Proxy has a similar functionality with RUN ON ALL to start queries
in parallel. So, I think it's a infrastructure commonly required.

--
Itagaki Takahiro


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

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: todo: plpgsql - tool to track code coverage
Следующее
От: Daniel Farina
Дата:
Сообщение: ALTER TABLE ... IF EXISTS feature?