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
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
Description: Digital signature
