Re: [PATCH] postgres_fdw extension support - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [PATCH] postgres_fdw extension support
Date
Msg-id CANP8+jLXzG+C=T6=u0d7eh+yrBGN2SizMimOrw=v-Ei+PsnTZQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] postgres_fdw extension support  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [PATCH] postgres_fdw extension support  (Paul Ramsey <pramsey@cleverelephant.ca>)
List pgsql-hackers
On 17 July 2015 at 01:23, Michael Paquier <michael.paquier@gmail.com> wrote:
 
> Well, as I see it there’s three broad categories of behavior available:
>
> 1- Forward nothing non-built-in (current behavior)
> 2- Use options to forward only specified non-built-in things (either in
> function chunks (extensions, as in this patch) or one-by-one (mark your
> desired functions / ops)
> 3- Forward everything if a “forward everything” option is set

Then what you are describing here is a parameter able to do a switch
among this selection:
- nothing, which is to check on built-in stuff
- extension list.
- all.

"all" seems to be a very blunt instrument but is certainly appropriate in some cases

I see an intermediate setting, giving four categories in total

0. Nothing, as now
1. Extension list option on the Foreign Server
2. Extension list option on the Foreign Data Wrapper, applies to all Foreign Servers of that type
3. All extensions allowed

I would imagine we would need Inclusion and Exclusion on each
e.g. +postgis, -postgis

Cat 2 and 3 would be merged to get the list for the specific server. That would allow you to a default for all servers of +postgis, yet set a specific server as -postgis, for example.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Beena Emerson
Date:
Subject: Re: Support for N synchronous standby servers - take 2
Next
From: Haribabu Kommi
Date:
Subject: Re: Parallel Seq Scan