<div dir="ltr"><div class="gmail_extra"><br />On Tue, Dec 31, 2013 at 9:38 AM, Pavel Stehule <<a
href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>>wrote:<br />><br />><br />> 2013/12/31
Fabríziode Royes Mello <<a href="mailto:fabriziomello@gmail.com">fabriziomello@gmail.com</a>><br /> >><br
/>>><br/>>> On Tue, Dec 31, 2013 at 9:08 AM, Pavel Stehule <<a
href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>>wrote:<br />>> ><br />>> >
Hello<br/>>> ><br /> >> > I am looking on this patch<br />>> ><br />>> > ALTER
TABLEfoo SET (ext.somext.do_replicate=true);<br />>> ><br />>> > Why is there fixed prefix "ext" ?<br
/>>>><br /> >> > This feature is similar to attaching setting to function<br />>> ><br
/>>>> CREATE OR REPLACE FUNCTION ... SET var = ...;<br />>> ><br />>> > We can use
someprefix.somegucwithout problems there.<br /> >> ><br />>><br />>> Hi,<br />>><br
/>>>We use the prefix "ext" (aka namespace) to distinguish these options which are related to "extensions".<br
/>>><br/>>> Have you seen the previous thread [1] ?<br /> ><br />><br />> yes, but I don't
understandwhy it is necessary? I use a analogy with custom GUC - and there we don't use similar prefix. Only any prefix
isrequired - and it can contain a dot.<br />><br /><br /> We use the namespace "ext" to the internal code
(src/backend/access/common/reloptions.c)skip some validations and store the custom GUC.<br /><br />Do you think we
don'tneed to use the "ext" namespace?<br /><br /><br />Regards,<br /><br />--<br />Fabrízio de Royes Mello<br
/>Consultoria/CoachingPostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/> >> Perfil Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a></div></div>
