Re: SQL/MED estimated time of arrival? - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: SQL/MED estimated time of arrival?
Date
Msg-id AANLkTin4Qb_iYmBiQD1DrmQw6G_hHqWXRj04bo-0QYU-@mail.gmail.com
Whole thread Raw
In response to Re: SQL/MED estimated time of arrival?  (Shigeru HANADA <hanada@metrosystems.co.jp>)
Responses Re: SQL/MED estimated time of arrival?
Re: SQL/MED estimated time of arrival?
List 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 by date:

Previous
From: Pavel Stehule
Date:
Subject: todo: plpgsql - tool to track code coverage
Next
From: Daniel Farina
Date:
Subject: ALTER TABLE ... IF EXISTS feature?