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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Daniel Bauman <danielbaniel(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Doc update proposal for the note on log_statement in the runtime config for logging page
Date: 2025-07-29 18:45:56
Message-ID: CAKFQuwbQtXm1Ft8D4C-vD1rR_ivyPFcYntahsXHxNUf-txdNLQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 29, 2025, 10:07 Daniel Bauman <danielbaniel(at)gmail(dot)com> wrote:

>
> The tradeoff to ignore errors and not fsync every log absolutely makes
> sense to me. It's just something it would be beneficial for users to be
> aware of. Particularly those concerned with auditing.
>

The main question is where to put such info. The config settings section
seems like an odd place to find that.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-29 19:23:37 Re: Regression with large XML data input
Previous Message Tomas Vondra 2025-07-29 18:45:38 Re: Reduce "Var IS [NOT] NULL" quals during constant folding