Re: SQL/MED estimated time of arrival?
Hitoshi Harada <umi.tanuki@gmail.com>
From: Hitoshi Harada <umi.tanuki@gmail.com>
To: Shigeru HANADA <hanada@metrosystems.co.jp>
Cc: Itagaki Takahiro <itagaki.takahiro@gmail.com>, Eric Davies <eric@barrodale.com>, pgsql-hackers@postgresql.org
Date: 2010-11-06T07:04:37Z
Lists: pgsql-hackers
2010/11/5 Shigeru HANADA <hanada@metrosystems.co.jp>: > On Fri, 5 Nov 2010 16:27:49 +0900 > Itagaki Takahiro <itagaki.takahiro@gmail.com> wrote: >> PL/Proxy has a similar functionality with RUN ON ALL to start queries >> in parallel. So, I think it's a infrastructure commonly required. > I noticed the lack of consideration about cache invalidation from > reading PL/Proxy source, thanks for your mention about PL/Proxy. :-) And if we really make this async query come true, I suggest designing resource (i.e. remote connection) management very carefully. When the executor fails in the middle of its execution, it possibly fails to release its own resource; close() in ExecutorEnd() will never be called. As far as I know files and memory are released automatically in the current mechanism, but MED APIs will use their own resources other than them. Regards, -- Hitoshi Harada