Horton

v1-0001-Update-docs-for-log_collector-about-error-cases.patch

application/octet-stream

Download
Filename: v1-0001-Update-docs-for-log_collector-about-error-cases.patch
Type: application/octet-stream
Part: 0
Message: Re: Doc update proposal for the note on log_statement in the runtime config for logging page

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →
Format: format-patch
Series: patch v1-0001
Subject: Update docs for log_collector about error cases.
File+−
doc/src/sgml/config.sgml 5 0 
From ff93b2ad2a690cb45bc7919a84ff2201e5bdc38c Mon Sep 17 00:00:00 2001
From: Daniel Bauman <danielbaniel@gmail.com>
Date: Thu, 7 May 2026 09:33:07 -0700
Subject: [PATCH v1] Update docs for log_collector about error cases.

Logs sent to the logging collector are not guaranteed
to be written to disk. While this may be obvious for anyone
with a technical understanding of how logging in postgresql
works this isn't obviuos to non-technical users of the db.

This doc attempts to make it clear that it's not transactionally
guaranteed that every committed transaction will be logged.
---
 doc/src/sgml/config.sgml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 73cc0412330..beb1bdadd1d 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -7066,6 +7066,11 @@ local0.*    /var/log/postgresql
           may fail to log some messages in such cases but it will not block
           the rest of the system.
         </para>
+        <para>
+          The logging collector writes to disk asynchronously. The server
+          losing power or errors when writing to the log file
+          can result in messages not being persisted.
+        </para>
        </note>
 
       </listitem>
-- 
2.50.1 (Apple Git-155)