database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00
Code Activity

doc: Clarify the logging collector's guarantees.

Browse Source 
Presently, the documentation for logging_collector says that the
collector "is designed to never lose messages," which reads as a
stronger promise than we actually make.  The collector does not
fsync the log file or retry failed writes, so log messages can go
missing after an operating system crash, power loss, or a write
error.  Reword that sentence and add a note about what is not
guaranteed.

Author: Daniel Bauman <danielbaniel@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Zhenwei Shang <a934172442@gmail.com>
Reviewed-by: Robert Treat <rob@xzilla.net>
Discussion: https://postgr.es/m/CAMtj0_a86DdDKkW-ReVpQpqjndVS6GMrwXVpQY4G3-SGY7saMQ%40mail.gmail.com
Backpatch-through: 14
This commit is contained in:
Nathan Bossart
2026-08-14 15:27:16 -05:00
parent d41b3e5865
commit 247ef8481d
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/config.sgml
View File

@@ -6808,7 +6808,7 @@ local0.* /var/log/postgresql
<note>
<para>
The logging collector is designed to never lose messages. This means
The logging collector is designed to avoid dropping messages. This means
that in case of extremely high load, server processes could be
blocked while trying to send additional log messages when the
collector has fallen behind. In contrast, <application>syslog</application>
@@ -6816,6 +6816,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 does not guarantee that log messages have
reached durable storage. It can still lose messages due to a system
crash, power loss, or an error while writing the log file.
</para>
</note>
</listitem>