<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 7, 2016 at 12:10 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">> On Fri, May 6, 2016 at 4:44 PM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> wrote:<br>
><br>
>> Usama,<br>
>><br>
>> Why do we need "PGPOOL" keyword? It seems to be annoying.<br>
>><br>
><br>
> Basically, there are two reasons. First,is there are some configuration<br>
> parameter names that are same in PostgreSQL and pgpool-II like<br>
> "port", "log_min_messages" and many others. So if we use the same syntax<br>
> without any difference, we would have no way of telling if the command is<br>
> referring to the pgpool-II or Backend.<br>
><br>
> like<br>
> SHOW port;<br>
> This command would be valid for both pgpool-II and PostgreSQL parameter.<br>
><br>
> Second, I think it's good to have distinction in commands for<br>
> setting/showing GUC and pgpool variables, otherwise it could cause the<br>
> confusions.<br>
<br>
</span>Ok, fair enough. BTW, I thought very limited number of pgpool<br>
variables can be changed by the "PGPOOL SET" command. Do you have<br>
complete list of such variable names which can be changed using<br>
"PGPOOL SET"?<br></blockquote><div><br></div><div>Thanks for looking into this. I have added the command with this syntax.</div><div><br></div><div>On the part of variables that can be changed for session only using the PGPOOL SET command I was thinking to start a separate discussion thread once the coding part is complete.</div><div><br></div><div>I have given a little thought on the parameters that we can allow to be changed through SET command and currently, I can only think of parameter related to life connection and child's lifetime that can be safely changed through SET command. i.e.</div><div class="gmail_quote"><br></div>--child_life_time<br>--client_idle_limit<br>--connection_life_time<br>--child_max_connections<br><br>But to finalize the list of parameters I think we should carefully consider each and every pgpool-II config parameter and its effect if it is changed for a particular session only.</div><div class="gmail_quote"><br></div><div class="gmail_quote">And it would be great to get your and the community input on making that list of parameters.</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Kind regards</div><div class="gmail_quote">Muhammad Usama</div><div class="gmail_quote"><br><br><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5"><br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
>> > Hi<br>
>> ><br>
>> > I am currently working on adding the SHOW and SET commands for pgpool-II<br>
>> > configuration parameter, these commands will allow the user to alter the<br>
>> > specific pgpool-II configuration parameter values for a user session.<br>
>> More<br>
>> > or less, these commands will work in similar ways as PostgreSQL's SET and<br>
>> > SHOW commands for PostgreSQL's GUC variables. I have already checked in<br>
>> the<br>
>> > configuration parameter framework to the pgpool master branch and before<br>
>> I<br>
>> > push the SET and SHOW command functionality I want the opinion on the<br>
>> > syntax of these two commands.<br>
>> ><br>
>> > I am thinking of using the PG's syntax with an addition of PGPOOL keyword<br>
>> > at the start<br>
>> ><br>
>> > For example<br>
>> ><br>
>> > PostgreSQL uses the following syntax for SHOW and SET command<br>
>> ><br>
>> > SHOW variable_name;<br>
>> > SHOW all;<br>
>> > SET variable_name to value;<br>
>> > SET variable_name to DEFAULT;<br>
>> > ..<br>
>> ><br>
>> > And for pgpool variables we can use<br>
>> ><br>
>> > PGPOOL SHOW variable_name;<br>
>> > PGPOOL SHOW all;<br>
>> > PGPOOL SET variable_name to value;<br>
>> > PGPOOL SET variable_name to DEFAULT;<br>
>> > ..<br>
>> ><br>
>> > Suggestions and thoughts.<br>
>> ><br>
>> > Kind Regards<br>
>> > Muhammad Usmaa<br>
>><br>
</div></div></blockquote></div><br></div></div>