From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Fabrízio Mello <fabriziomello(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: [PATCH] Store Extension Options |
Date: | 2013-12-31 11:38:34 |
Message-ID: | CAFj8pRAtxh9mAGGq-dv=SWQfoSEjdyHZD0g6nvpd0Ki1RT3bLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/12/31 Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
>
> On Tue, Dec 31, 2013 at 9:08 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> >
> > Hello
> >
> > I am looking on this patch
> >
> > ALTER TABLE foo SET (ext.somext.do_replicate=true);
> >
> > Why is there fixed prefix "ext" ?
> >
> > This feature is similar to attaching setting to function
> >
> > CREATE OR REPLACE FUNCTION ... SET var = ...;
> >
> > We can use someprefix.someguc without problems there.
> >
>
> Hi,
>
> We use the prefix "ext" (aka namespace) to distinguish these options which
> are related to "extensions".
>
> Have you seen the previous thread [1] ?
>
yes, but I don't understand why it is necessary? I use a analogy with
custom GUC - and there we don't use similar prefix. Only any prefix is
required - and it can contain a dot.
Regards
Pavel
>
> Regards,
>
> [1]
> http://www.postgresql.org/message-id/CAFcNs+rqCq1H5eXW-cvdti6T-xo2STEkhjREx=OdmAkK5tiOOw@mail.gmail.com
>
> --
> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2013-12-31 12:30:16 | Re: [PATCH] Store Extension Options |
Previous Message | Fabrízio de Royes Mello | 2013-12-31 11:32:59 | Re: [PATCH] Store Extension Options |