Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X1sWv-0000So-1D for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Jul 2014 07:31:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X1sWu-0004rh-HE for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Jul 2014 07:31:04 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X1sWt-0004rW-4H for pgsql-hackers@postgresql.org; Tue, 01 Jul 2014 07:31:03 +0000 Received: from tama50.ecl.ntt.co.jp ([129.60.39.147]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X1sWp-0004jY-53 for pgsql-hackers@postgresql.org; Tue, 01 Jul 2014 07:31:01 +0000 Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id s617Utgn032019; Tue, 1 Jul 2014 16:30:55 +0900 Received: from mfs6.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 55F6FE0140; Tue, 1 Jul 2014 16:30:55 +0900 (JST) Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 4972EE0139; Tue, 1 Jul 2014 16:30:55 +0900 (JST) Received: from [129.60.241.75] ([129.60.241.75]) by imail3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id s617Uttm018040; Tue, 1 Jul 2014 16:30:55 +0900 Message-ID: <53B263A1.3060107@lab.ntt.co.jp> Date: Tue, 01 Jul 2014 16:30:41 +0900 From: Etsuro Fujita User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ashutosh Bapat CC: Kyotaro HORIGUCHI , Shigeru Hanada , pgsql-hackers Subject: Re: inherit support for foreign tables References: <53393E18.3080901@lab.ntt.co.jp> <533C01C7.6030809@lab.ntt.co.jp> <53706FB6.6000403@lab.ntt.co.jp> <20140620.170406.123403564.horiguchi.kyotaro@lab.ntt.co.jp> <53A92924.90702@lab.ntt.co.jp> <53B10914.2010504@lab.ntt.co.jp> <53B1405F.7040203@lab.ntt.co.jp> <53B21861.1000706@lab.ntt.co.jp> <53B25B6C.7020504@lab.ntt.co.jp> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org (2014/07/01 16:04), Ashutosh Bapat wrote: > On Tue, Jul 1, 2014 at 12:25 PM, Etsuro Fujita > > wrote: > Maybe I'm missing something, but what's the point of using the > tlist, not reltargetlist? > Compliance with other create_*scan_plan() functions. The tlist passed to > those functions is sometimes preprocessed in create_scan_plan() and some > of the function it calls. If we use reltargetlist directly, we loose > that preprocessing. I have not see any of create_*scan_plan() fetch the > targetlist directly from RelOptInfo. It is always the one supplied by > build_path_tlist() or disuse_physical_tlist() (which in turn calls > build_path_tlist()) or build_physical_tlist(). I've got the point. As I said upthread, I'll work on calculating attr_needed for child rels, and I hope that that will eliminate your concern. Thanks, Best regards, Etsuro Fujita -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers