Re: [PATCH] postgres_fdw extension support

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] postgres_fdw extension support
Date: 2015-07-16 14:06:10
Message-ID: 3422.1437055570@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> writes:
> On 2015-07-16 PM 12:43, Tom Lane wrote:
>> The basic issue here is "how can a user control which functions/operators
>> can be sent for remote execution?". While it's certainly true that
>> sometimes you might want function-by-function control of that, Paul's
>> point was that extension-level granularity would be extremely convenient
>> for PostGIS, and probably for other extensions.

> Perhaps just paranoid but is the extension version number any significant?

In any scenario for user control of sending functions to the far end, it's
on the user's head to make sure that he's telling us the truth about which
functions are compatible between local and remote servers. That would
extend to checking cross-version compatibility if he's running different
versions, too. We already have risks of that kind with built-in
functions, really, and I've not heard complaints about it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2015-07-16 14:16:07 Re: [PATCH] postgres_fdw extension support
Previous Message Amit Langote 2015-07-16 14:02:06 Re: TABLESAMPLE patch is really in pretty sad shape