Re: postgres_fdw behaves oddly

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres_fdw behaves oddly
Date: 2014-11-19 07:40:31
Message-ID: 546C496F.7070503@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2014/11/19 15:56), Ashutosh Bapat wrote:
> On Wed, Nov 19, 2014 at 12:14 PM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp <mailto:fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>> wrote:
> (2014/11/19 14:58), Ashutosh Bapat wrote:

> May be we should modify use_physical_tlist() to return
> false in
> case of RELKIND_FOREIGN_TABLE, so that we can use tlist in
> create_foreignscan_plan(). I do not see any create_*_plan() function
> using reltargetlist directly.

> Yeah, I think we can do that, but I'm not sure that we should use
> tlist in create_foreignscan_plan(), not rel->reltargetlist. How
> about leaving this for committers to decide.

> I am fine with that. May be you want to add an XXX comment there to
> bring it to the committer's notice.

It's ok, but I'm not convinced with your idea. So, I think the comment
can be adequately described by you, not by me. So, my proposal is for
you to add the comment to the CF app. Could you do that?

Thanks,

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2014-11-19 08:15:42 Re: PostgreSQL doesn't stop propley when --slot option is specified with pg_receivexlog.
Previous Message Etsuro Fujita 2014-11-19 06:58:59 Re: postgres_fdw behaves oddly