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

From Fabrízio de Royes Mello
Subject Re: [PATCH] Store Extension Options
Date
Msg-id CAFcNs+peZkCNu_HDGin+EgGUdC7ZtPd+KY5NisvGbQkEPTDVgg@mail.gmail.com
Whole thread
In response to Re: [PATCH] Store Extension Options  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Store Extension Options
List pgsql-hackers

On Thu, Nov 21, 2013 at 12:05 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Wed, Nov 20, 2013 at 1:52 PM, Fabrízio de Royes Mello
> <fabriziomello@gmail.com> wrote:
> > The main goal of this patch is enable to an user the capability to store
> > options
> > (relations and attributes) related to extensions by using a fixed prefix
> > called 'ext' in
> > the defined name. It's cant be useful for replication solutions.
> >
> > 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?


> 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.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UNNEST with multiple args, and TABLE with multiple funcs
Next
From: Tom Lane
Date:
Subject: Re: UNNEST with multiple args, and TABLE with multiple funcs