From 30985afc0acb34ccd92a818b42468ef8be4a8151 Mon Sep 17 00:00:00 2001
From: Sebastian Harl <sh@tokkee.org>
Date: Thu, 15 Nov 2012 13:36:52 +0100
Subject: [PATCH] collectd.conf(5): Documented the postgresql FLUSH support.

---
 src/collectd.conf.pod | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod
index be130320..517d4948 100644
--- a/src/collectd.conf.pod
+++ b/src/collectd.conf.pod
@@ -3856,6 +3856,24 @@ causes all collected data to be send to the database using the settings
 defined in the writer configuration (see the section "FILTER CONFIGURATION"
 below for details on how to selectively send data to certain plugins).
 
+Each writer will register a flush callback which may be used when having long
+transactions enabled (see the B<CommitInterval> option above). When issuing
+the B<FLUSH> command (see L<collectd-unixsock(5)> for details) the current
+transaction will be committed right away. Two different kinds of flush
+callbacks are available with the C<postgresql> plugin:
+
+=over 4
+
+=item B<postgresql>
+
+Flush all writer backends.
+
+=item B<postgresql->I<database>
+
+Flush all writers of the specified I<database> only.
+
+=back
+
 =back
 
 =head2 Plugin C<powerdns>
-- 
2.11.0