From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Fabrízio Mello <fabriziomello(at)gmail(dot)com> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Store Extension Options |
Date: | 2013-11-21 13:06:07 |
Message-ID: | CA+TgmoY=Mnnr+2_sFxvYWdqU_T_AaYkm+ZYsorBY0S+aSZUj2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 20, 2013 at 9:35 PM, Fabrízio de Royes Mello
<fabriziomello(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2013-11-21 13:15:28 | WIP patch for updatable security barrier views |
Previous Message | Fujii Masao | 2013-11-21 12:58:41 | Re: -d option for pg_isready is broken |