public inbox for [email protected]
help / color / mirror / Atom feedsynchronous_standby_names and hot_standby_feedback
2+ messages / 2 participants
[nested] [flat]
* synchronous_standby_names and hot_standby_feedback
@ 2011-06-13 10:29 Fujii Masao <[email protected]>
2011-06-13 16:26 ` Re: synchronous_standby_names and hot_standby_feedback Robert Haas <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Fujii Masao @ 2011-06-13 10:29 UTC (permalink / raw)
To: pgsql-docs
Hi,
The GucContext of synchronous_standby_names and hot_standby_feedback
is PGC_SIGHUP, so the following should be added into the explanations about
those parameters. Attached patch does that.
---------------------
This parameter can only be set in the <filename>postgresql.conf</>
file or on the server command line.
---------------------
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachments:
[text/x-patch] improve_doc_v1.patch (1.6K, 2-improve_doc_v1.patch)
download | inline diff:
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
***************
*** 2107,2112 **** SET ENABLE_SEQSCAN TO OFF;
--- 2107,2116 ----
<xref linkend="guc-synchronous-commit"> parameter to
<literal>local</> or <literal>off</>.
</para>
+ <para>
+ This parameter can only be set in the <filename>postgresql.conf</>
+ file or on the server command line.
+ </para>
</listitem>
</varlistentry>
***************
*** 2239,2246 **** SET ENABLE_SEQSCAN TO OFF;
about queries currently executing on the standby. This parameter can
be used to eliminate query cancels caused by cleanup records, but
can cause database bloat on the primary for some workloads.
! The default value is <literal>off</literal>. Feedback messages will not
! be sent more frequently than once per <varname>wal_receiver_status_interval</>.
</para>
</listitem>
</varlistentry>
--- 2243,2252 ----
about queries currently executing on the standby. This parameter can
be used to eliminate query cancels caused by cleanup records, but
can cause database bloat on the primary for some workloads.
! Feedback messages will not be sent more frequently than once per
! <varname>wal_receiver_status_interval</>. The default value is
! <literal>off</literal>. This parameter can only be set in the
! <filename>postgresql.conf</> file or on the server command line.
</para>
</listitem>
</varlistentry>
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: synchronous_standby_names and hot_standby_feedback
2011-06-13 10:29 synchronous_standby_names and hot_standby_feedback Fujii Masao <[email protected]>
@ 2011-06-13 16:26 ` Robert Haas <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Robert Haas @ 2011-06-13 16:26 UTC (permalink / raw)
To: Fujii Masao <[email protected]>; +Cc: pgsql-docs
On Mon, Jun 13, 2011 at 6:29 AM, Fujii Masao <[email protected]> wrote:
> The GucContext of synchronous_standby_names and hot_standby_feedback
> is PGC_SIGHUP, so the following should be added into the explanations about
> those parameters. Attached patch does that.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2011-06-13 16:26 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-06-13 10:29 synchronous_standby_names and hot_standby_feedback Fujii Masao <[email protected]>
2011-06-13 16:26 ` Robert Haas <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox