From: Sebastian Harl <sh@tokkee.org>
Date: Wed, 14 Nov 2012 18:51:41 +0000 (+0100)
Subject: collectd.conf(5): Documented the "CommitInterval" option of 'postgresql'.
X-Git-Tag: collectd-5.2.0~13^2~11
X-Git-Url: https://git.verplant.org/?a=commitdiff_plain;h=4a9d11514a7e95d89dafc3f7f5f4610e707ae9e3;p=collectd.git

collectd.conf(5): Documented the "CommitInterval" option of 'postgresql'.
---

diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index ca4dcd53..29a1d145 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -3511,6 +3511,7 @@ L<http://www.postgresql.org/docs/manuals/>.
     <Database qux>
       # ...
       Writer sqlstore
+      CommitInterval 10
     </Database>
   </Plugin>
 
@@ -3766,6 +3767,17 @@ for details.
 Specify the interval with which the database should be queried. The default is
 to use the global B<Interval> setting.
 
+=item B<CommitInterval> I<seconds>
+
+This option may be used for database connections which have "writers" assigned
+(see above). If specified, it causes a writer to put several updates into a
+single transaction. This transaction will last for the specified amount of
+time. By default, each update will be executed in a separate transaction. Each
+transaction generates a fair amount of overhead which can, thus, be reduced by
+activating this option. The draw-back is, that data covering the specified
+amount of time will be lost, for example, if a single statement within the
+transaction fails or if the database server crashes.
+
 =item B<Host> I<hostname>
 
 Specify the hostname or IP of the PostgreSQL server to connect to. If the