diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 645cbb9..ba635f4 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4149,6 +4149,32 @@ SELECT * FROM parent WHERE key = 2400;
     a convenient way to find and access log content without establishing a
     database connection.</para>
 
+    <note>
+      <indexterm>
+        <primary><filename>current_logfiles</filename></primary>
+        <secondary>in relation to <application>systemd</application></secondary>
+      </indexterm>
+      <indexterm>
+        <primary><function>pg_current_logfile</function></primary>
+        <secondary>in relation to <application>systemd</application></secondary>
+      </indexterm>
+      <indexterm>
+        <primary>systemd</primary>
+        <secondary>Logging and logfiles</secondary>
+      </indexterm>
+
+      <para><filename>current_logfiles</filename> exists only
+      when <xref linkend="guc-logging-collector"> is <literal>on</literal>.
+      The <varname>logging_collector</varname> default,
+      in <productname>PostgreSQL</productname> and in many binary
+      distributions, is <literal>off</literal>.
+      Many <productname>Linux</productname> distributions' default is to leave
+      the logging collector off and rely on <application>systemd</application>
+      to collect <filename>stderr</filename> and manage logging.  This default
+      affects the <xref linkend="functions-info-pg-current-logfile"> function
+      as well.</para>
+    </note>
+
     <sect2 id="runtime-config-logging-where">
      <title>Where To Log</title>
 
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 5e0a088..bbd3ecd 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -15682,7 +15682,8 @@ SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ..
     <secondary>pg_current_logfile function</secondary>
    </indexterm>
 
-   <para>
+   <para id="functions-info-pg-current-logfile"
+         xreflabel="pg_current_logfile">
     <function>pg_current_logfile</function> returns, as <type>text</type>,
     the path of either the csv or stderr log file currently in use by the
     logging collector.  This is a path including the