Re: Extension support for postgres_fdw

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extension support for postgres_fdw
Date: 2015-06-20 16:53:16
Message-ID: 59503.1434819196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 20 June 2015 at 18:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The key question here is whether filtering functions/operators at the
>> level of extensions is a good design. It seems to me like a reasonable
>> compromise between flexibility and ease of use, but others might see it
>> differently.

> I like that, but currently we handle things in terms of Schemas. It would
> be strange to have differing ways of specifying groups of objects. Maybe
> that's not a problem, but we'd probably need to analyse that to make sure
> it didn't make things more complex.

Fair point, but I think making it schema-based would be pretty awkward
for many common use-cases. By default, at least, all extensions get
dropped into schema public. I doubt it would be a good idea to say
"anything in public is transmittable".

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-06-20 16:55:44 Re: pretty bad n_distinct estimate, causing HashAgg OOM on TPC-H
Previous Message Simon Riggs 2015-06-20 16:45:30 Re: Extension support for postgres_fdw