<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 6, 2016 at 4:44 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Usama,<br>
<br>
Why do we need "PGPOOL" keyword? It seems to be annoying.<br></blockquote><div><br></div><div>Basically, there are two reasons. First,is there are some configuration parameter names that are same in PostgreSQL and pgpool-II like</div><div>"port", "log_min_messages" and many others. So if we use the same syntax without any difference, we would have no way of telling if the command is referring to the pgpool-II or Backend.</div><div><br></div><div>like</div><div>SHOW port;</div><div>This command would be valid for both pgpool-II and PostgreSQL parameter.</div><div><br></div><div>Second, I think it's good to have distinction in commands for setting/showing GUC and pgpool variables, otherwise it could cause the confusions. </div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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>
<div class="HOEnZb"><div class="h5">> 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. 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 the<br>
> configuration parameter framework to the pgpool master branch and before 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>
</div></div></blockquote></div><br></div></div>