[pgpool-hackers: 1864] Re: Difference between .html and .sgml

Muhammad Usama m.usama at gmail.com
Wed Oct 19 16:28:04 JST 2016


On Wed, Oct 19, 2016 at 12:25 PM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > Hi
> >
> > On Tue, Oct 18, 2016 at 6:23 AM, Tatsuo Ishii <ishii at sraoss.co.jp>
> wrote:
> >
> >> Usama,
> >>
> >> While reading 3.6 docs, I noticed the difference between .html and
> >> .sgml for some items.
> >>
> >> For example, log_statement.
> >>
> >> HTML:
> >>         <p>
> >>         You need to reload pgpool.conf if you change this value. And you
> >> can also use PGPOOL SET command
> >>         to alter the value of this parameter for a current session.
> >>         </p>
> >>
> >> SGML:
> >>         This parameter can be changed by reloading the pgpool
> >> configurations.
> >>
> >> Same thing can be said to other parameters.
> >>
> >> log_per_node_statement, check_temp_table, check_unlogged_table,
> >> allow_sql_comments, client_idle_limit, log_error_verbosity,
> >> client_min_messages, log_min_messages, client_idle_limit_in_recovery.
> >>
> >
> > Oh Sorry I missed it by mistake, Attached is the patch for the fix.
> >
> >
> >>
> >> Also, I cannot find explanations for which items are usable for new
> >> PGPOOL SET/RESET.
> >>
> >
> > I was of the point of view, that defining about how a variable value can
> be
> > changed (i.e at server start, or by reloading configuration or by PGPOOL
> > SET/RESET) in the document section of the configuration parameter's is
> > enough. So I haven't added any new documentation section for that.
>
> Sounds good.
>
> Thanks, I have committed the changes

Regards,


> > Do you also want to list down all the configuration parameters that can
> be
> > changed by PGPOOL SET/RESET separately?
>
> No.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20161019/f251bb68/attachment.html>


More information about the pgpool-hackers mailing list