From: Andres Freund <andres@anarazel.de>
Date: Fri, 24 Mar 2023 21:18:40 +0000 (-0700)
Subject: docs: Explain how to silence overly verbose messages by fop
X-Git-Tag: REL_16_BETA1~432
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=642d8779768ecddc2917747940885d11f844f6e9;p=thirdparty%2Fpostgresql.git

docs: Explain how to silence overly verbose messages by fop

Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/20230324194701.dqkzcdtlcikseo22@awork3.anarazel.de
---

diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml
index 35c4afc81ad..261952085e2 100644
--- a/doc/src/sgml/docguide.sgml
+++ b/doc/src/sgml/docguide.sgml
@@ -373,6 +373,16 @@ ADDITIONAL_FLAGS='-Xmx1500m'
     swapping or will not work at all.
    </para>
 
+   <para>
+    In its default configuration <productname>FOP</productname> will emit an
+    <literal>INFO</literal> message for each page. The log level can be
+    changed via <filename>~/.foprc</filename>:
+<programlisting>
+LOGCHOICE=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
+LOGLEVEL=-Dorg.apache.commons.logging.simplelog.defaultlog=WARN
+</programlisting>
+   </para>
+
    <para>
     Other XSL-FO processors can also be used manually, but the automated build
     process only supports FOP.