Re: Doc update proposal for the note on log_statement in the runtime config for logging page

On Fri, Aug 14, 2026 at 2:24 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Fri, Aug 14, 2026 at 01:24:46PM -0400, Robert Treat wrote:
> > I think there's general agreement that these changes help clarify both
> > the intent and the real world operation of the logging collector. I
> > played around with the wording a little, but I couldn't find anything
> > that seemed markedly better, so outside of some small kibitzing (line
> > wrapping, maybe some commas) I think this is probably ready for
> > commit, and I've marked it as such in the commitfest.
>
> How about something like this?
>
> 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, syslog prefers to drop messages if it
> cannot write them, which means it may fail to log some messages in such
> cases but it will not block the rest of the system.
>
> 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.
>
> IMHO the overall style of this section still has some room for improvement,
> but I think it gets the point across well enough.
>

+1

Robert Treat
https://xzilla.net