Re: FDW for PostgreSQL

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Kohei KaiGai *EXTERN*" <kaigai(at)kaigai(dot)gr(dot)jp>, "Shigeru Hanada" <shigeru(dot)hanada(at)gmail(dot)com>
Cc: "Etsuro Fujita" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FDW for PostgreSQL
Date: 2012-11-22 09:37:52
Message-ID: D960CB61B694CF459DCFB4B0128514C208B88716@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kohei KaiGai wrote:
> 2012/11/22 Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>:
>> After playing with some big SQLs for testing, I came to feel that
>> showing every remote query in EXPLAIN output is annoying, especially
>> when SELECT * is unfolded to long column list.
>>
>> AFAIK no plan node shows so many information in a line, so I'm
>> inclined to make postgres_fdw to show it only when VERBOSE was
>> specified. This would make EXPLAIN output easy to read, even if many
>> foreign tables are used in a query.
>>
>> Thoughts?
>>
> Indeed, I also think it is reasonable solution.

+1

That's the way I do it for oracle_fdw.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2012-11-22 10:06:52 Re: [PATCH] Make pg_basebackup configure and start standby [Review]
Previous Message Kohei KaiGai 2012-11-22 09:30:06 Re: FDW for PostgreSQL