Re: [PATCH] Store Extension Options - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Store Extension Options
Date
Msg-id 1389415627.12505.11.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: [PATCH] Store Extension Options  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: [PATCH] Store Extension Options  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-hackers
On Sat, 2014-01-11 at 00:48 -0200, Fabrízio de Royes Mello wrote:
> > Now, if bdr is installed but the validation doesn't happen unless
> bdr
> > is "loaded" in some sense, then that is an implementation deficiency
> > that I think we can insist be rectified before this feature is
> accepted.
> >

> Check if extension is already installed is not enough for the first
> version of this feature?

Elsewhere it was argued that tying this to extensions is not
appropriate.  I agree.

It depends on how this feature is supposed to be used exactly.  A
replication plugin might very well be loaded via
session_preload_libraries and not appear in SQL at all.  In that case
you need some C-level hook.  In another case, an extension might want to
inspect relation options from user-space triggers.  So you'd need to
register some SQL-level function for option validation.

This could end up being two separate but overlapping features.




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Next
From: Greg Stark
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE