Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 106B16576E
	for <pgsql-hackers@postgresql.org>;
	Tue, 31 Jul 2012 09:23:23 -0300 (ADT)
Received: from tama500.ecl.ntt.co.jp ([129.60.39.148])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <fujita.etsuro@lab.ntt.co.jp>) id 1SwBTt-0002AQ-HR
	for pgsql-hackers@postgresql.org; Tue, 31 Jul 2012 12:23:23 +0000
Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144])
	by tama500.ecl.ntt.co.jp (8.14.5/8.14.5) with ESMTP id
	q6VCN3C4003323; Tue, 31 Jul 2012 21:23:03 +0900 (JST)
Received: from mfs5.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id AEA8FE00EF;
	Tue, 31 Jul 2012 21:23:03 +0900 (JST)
Received: from dmailsv1.y.ecl.ntt.co.jp (dmailsv1.y.ecl.ntt.co.jp
	[129.60.53.14])
	by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id A18B6E00ED;
	Tue, 31 Jul 2012 21:23:03 +0900 (JST)
Received: from mailsv11.y.ecl.ntt.co.jp
	by dmailsv1.y.ecl.ntt.co.jp (8.14.5/dmailsv1-2.1) with ESMTP id
	q6VCN3h7005353; Tue, 31 Jul 2012 21:23:03 +0900 (JST)
Received: from localhost
	by mailsv11.y.ecl.ntt.co.jp (8.14.5/Lab-1.9) with ESMTP id
	q6VCN3s4001123; Tue, 31 Jul 2012 21:23:03 +0900 (JST)
From: "Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp>
To: "'Kohei KaiGai'" <kaigai@kaigai.gr.jp>
Cc: "'Shigeru HANADA'" <shigeru.hanada@gmail.com>,
	"'PostgreSQL-development'" <pgsql-hackers@postgresql.org>
References: <4FD9D947.1020803@gmail.com>
	<CADyhKSXs3d-2mvM=5c_GpehQd_nULL-GbGggLVeVKNn5R6odjA@mail.gmail.com>
	<CADyhKSViO=i5tMQWS=bvAdkY6ugZs9p7Cd-sdCrc3jRPeZjD8g@mail.gmail.com>
	<002301cd6016$971671f0$c54355d0$@lab.ntt.co.jp>
	<CADyhKSXFtPTtgcTa_c3CCyOGYwSaeVrdypLRtCPTRpgQNkUrnw@mail.gmail.com>
In-Reply-To: 
 <CADyhKSXFtPTtgcTa_c3CCyOGYwSaeVrdypLRtCPTRpgQNkUrnw@mail.gmail.com>
Subject: Re: pgsql_fdw in contrib
Date: Tue, 31 Jul 2012 21:28:27 +0900
Message-ID: <002d01cd6f17$fcb00f20$f6102d60$@lab.ntt.co.jp>
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ24NQWutH15ElQlYtp4yJvebFgtwGTFppjAhoTPw8CpoaDNQD6Jy0SlbX91vA=
Content-Language: ja
X-Pg-Spam-Score: -0.5 (/)
X-Archive-Number: 201207/1125
X-Sequence-Number: 211808

Hi KaiGai-san,

Sorry about the delay in answering.  I have been swamped with another thing
lately.

> BTW, your patch does not make sense in my environment that is just
> after initdb without any parameter customizing. Could you give us
> the step to reproduce the Nested-Loop plan from Hash-Join?

I examined both the Nested-Loop and Hash-Join plans by using the enable_xxxxx
options, and found that their total costs are almost equal.  The result might
depend on the execution environment (My environment is Linux 2.6.18 on x86_64.).
I think it is preferable to use the enable_xxxxx options for this regression
test like src/test/regress/sql/join.sql.

Thanks,

Best regards,
Etsuro Fujita