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

From Tom Lane
Subject Re: [PATCH] postgres_fdw extension support
Date
Msg-id 23074.1446580676@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] postgres_fdw extension support  (Paul Ramsey <pramsey@cleverelephant.ca>)
Responses Re: [PATCH] postgres_fdw extension support  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Paul Ramsey <pramsey@cleverelephant.ca> writes:
> [ 20151006b_postgres_fdw_extensions.patch ]

Starting to look through this now.  I'm dubious of the decision to have
ExtractExtensionList throw errors if there are un-installed extensions
mentioned in the FDW options.  Wouldn't it be a lot more convenient if
such extension names were silently ignored?  You cannot guarantee that the
list is always up to date anyway; consider creating a server, setting some
extension options, and then dropping some of those extensions.  Moreover,
the current semantics create a hazard for pg_dump, which can't reasonably
be expected to know that it must restore extensions X and Y before it can
create foreign server Z.

There might be a case for raising a WARNING during
postgres_fdw_validator(), but no more than that, IMO.  Certainly ERROR
during regular use of the server is right out.

Comments?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Minor clarifying changes to abbreviated key abort code comments
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] postgres_fdw extension support