pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Joshua Tolley <eggyknap@gmail.com>
To: pgsql-docs@postgresql.org
Subject: commit_delay and commit_siblings -- restart or reload?
Date: Tue, 1 Jun 2010 09:51:02 -0600
Message-ID: <4c052c68.20a5720a.3577.33e6@mx.google.com> (raw)

The documentation for commit_delay and commit_siblings doesn't mention whether
a reload or restart is required to set them. I recommend something like the
trivial attached docs patch to make it clear(er) that a reload is required.

--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com

Attachments:

commit_delay.docs.patch (text/x-diff, 1.8K) download
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 48ad9f6..c513eba 100644
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** SET ENABLE_SEQSCAN TO OFF;
*** 1643,1649 ****
          commit. Therefore, the delay is only performed if at least
          <varname>commit_siblings</varname> other transactions are
          active at the instant that a server process has written its
!         commit record. The default is zero (no delay).
         </para>
        </listitem>
       </varlistentry>
--- 1643,1651 ----
          commit. Therefore, the delay is only performed if at least
          <varname>commit_siblings</varname> other transactions are
          active at the instant that a server process has written its
!         commit record. The default is zero (no delay). This parameter can only
!         be set in the <filename>postgresql.conf</> file or on the server
!         command line.
         </para>
        </listitem>
       </varlistentry>
*************** SET ENABLE_SEQSCAN TO OFF;
*** 1659,1665 ****
          before performing the <varname>commit_delay</> delay. A larger
          value makes it more probable that at least one other
          transaction will become ready to commit during the delay
!         interval. The default is five transactions.
         </para>
        </listitem>
       </varlistentry>
--- 1661,1669 ----
          before performing the <varname>commit_delay</> delay. A larger
          value makes it more probable that at least one other
          transaction will become ready to commit during the delay
!         interval. The default is five transactions. This parameter can only be
!         set in the <filename>postgresql.conf</> file or on the server command
!         line.
         </para>
        </listitem>
       </varlistentry>

  signature.asc (application/pgp-signature, 196B) download

view thread (3+ messages)  latest in thread

Message-ID: <4c052c68.20a5720a.3577.33e6@mx.google.com>
Permalink:  ../4c052c68.20a5720a.3577.33e6@mx.google.com/
Also on:    postgresql.org/message-id/4c052c68.20a5720a.3577.33e6@mx.google.com

copy link · copy postgr.es · copy git am

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: eggyknap@gmail.com
  Subject: Re: commit_delay and commit_siblings -- restart or reload?
  In-Reply-To: <4c052c68.20a5720a.3577.33e6@mx.google.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox