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

From Robert Haas
Subject Re: [PATCH] Store Extension Options
Date
Msg-id CA+TgmoY=Mnnr+2_sFxvYWdqU_T_AaYkm+ZYsorBY0S+aSZUj2g@mail.gmail.com
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
List pgsql-hackers
On Wed, Nov 20, 2013 at 9:35 PM, Fabrízio de Royes Mello
<fabriziomello@gmail.com> wrote:
>> > So, with this patch we can do that:
>> >
>> > ALTER TABLE foo
>> >    SET (ext.somext.do_replicate=true);
>> >
>> > When 'ext' is the fixed prefix, 'somext' is the extension name,
>> > 'do_replicate' is the
>> > extension option and 'true' is the value.
>>
>> This doesn't seem like a particular good choice of syntax;
>
> What's your syntax suggestion?

I dunno, but I doubt that hardcoding ext as an abbreviation for
extension is a good decision.  I also doubt that any fixed prefix is a
good decision.

>> and I also have my doubts about the usefulness of the feature.
>
> This feature can be used for replication solutions, but also can be used for
> any extension that need do some specific configuration about tables,
> attributes and/or indexes.

So, create your own configuration table with a column of type regclass.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: -d option for pg_isready is broken
Next
From: Craig Ringer
Date:
Subject: WIP patch for updatable security barrier views