pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: robertmhaas@gmail.com
Cc: amitdkhan.pg@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: asynchronous execution
Date: Thu, 16 Mar 2017 16:17:03 -0400
Message-ID: <22644.1489695423@sss.pgh.pa.us> (raw)
In-Reply-To: <CADkLM=cqfQL5+CDa6eVqNvM2oNXCR8gcgTML2r7mpetGx_e6GA@mail.gmail.com>
References: <9058d70b-a6b0-8b3c-091a-fe77ed0df580@lab.ntt.co.jp>
	<20170216.210600.214980879.horiguchi.kyotaro@lab.ntt.co.jp>
	<20170222.173945.262776579.horiguchi.kyotaro@lab.ntt.co.jp>
	<20170223.205925.120810176.horiguchi.kyotaro@lab.ntt.co.jp>
	<CADkLM=eHssZhc2tC4t6C=8uGn2LV=NE6LuzavZc3+=mFW0AC0A@mail.gmail.com>
	<7847e2c8-2d8b-c692-4e0b-2544887ba606@lab.ntt.co.jp>
	<CADkLM=dCp=JRAjiC5bcH2c5Ug3EOMrdDs+CiyZjogOHkHCfH8Q@mail.gmail.com>
	<CADkLM=ffokmXLdc3QRAs74zLC84AE1YWWnWGOt9PQ8osTzzs1w@mail.gmail.com>
	<dd705978-add0-7503-e78c-2ae78f6e869d@lab.ntt.co.jp>
	<CADkLM=fDOTnmJO4YQhvqMGoRGVzkCzZ0r0r4SUzM6aJn=d7x_g@mail.gmail.com>
	<e7dc8128-f32b-ff9a-870e-f1117b8e4fa6@lab.ntt.co.jp>
	<CADkLM=cqfQL5+CDa6eVqNvM2oNXCR8gcgTML2r7mpetGx_e6GA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Corey Huinker <corey.huinker@gmail.com> writes:
> I reworked the test such that all of the foreign tables inherit from the
> same parent table, and if you query that you do get async execution. But It
> doesn't work when just stringing together those foreign tables with UNION
> ALLs.

> I don't know how to proceed with this review if that was a goal of the
> patch.

Whether it was a goal or not, I'd say there is something either broken
or incorrectly implemented if you don't see that.  The planner (and
therefore also the executor) generally treats inheritance the same as
simple UNION ALL.  If that's not the case here, I'd want to know why.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (65+ messages)  latest in thread

Message-ID: <22644.1489695423@sss.pgh.pa.us>
Permalink:  ../22644.1489695423@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22644.1489695423@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, corey.huinker@gmail.com, Langote_Amit_f8@lab.ntt.co.jp, horiguchi.kyotaro@lab.ntt.co.jp, robertmhaas@gmail.com, amitdkhan.pg@gmail.com
  Subject: Re: asynchronous execution
  In-Reply-To: <22644.1489695423@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox