Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit19fd0c2

Browse files
committed
Add note that the logging collector can block backends in high load situations.
1 parentf82d4d5 commit19fd0c2

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

‎doc/src/sgml/config.sgml

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.225 2009/09/08 17:08:36 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.226 2009/09/10 15:02:46 alvherre Exp $ -->
22

33
<chapter Id="runtime-config">
44
<title>Server Configuration</title>
@@ -2422,6 +2422,19 @@ local0.* /var/log/postgresql
24222422
is dynamic-linker failure messages).
24232423
This parameter can only be set at server start.
24242424
</para>
2425+
2426+
<note>
2427+
<para>
2428+
The logging collector is designed to never lose messages. This means
2429+
that in case of extremely high load, server processes could be
2430+
blocked due to trying to send additional log messages when the
2431+
collector has fallen behind. In contrast, <application>syslog</>
2432+
prefers to drop messages if it cannot write them, which means it's
2433+
less reliable in those cases but it will not block the rest of the
2434+
system.
2435+
</para>
2436+
</note>
2437+
24252438
</listitem>
24262439
</varlistentry>
24272440

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp