On Tue, Jul 29, 2025 at 11:46 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
>
>
> On Tue, Jul 29, 2025, 10:07 Daniel Bauman wrote:
>
>>
>> The tradeoff to ignore errors and not fsync every log absolutely makes
>> sense to me. It's just somethi
On Tue, Jul 29, 2025 at 8:46 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Monday, July 28, 2025, Daniel Bauman wrote:
>
>> The doc fragment you shared is explaining to customers that basic syntax
>> checks are done before postgres gets to logging the
correctly or am I on the wrong codepath?
-Daniel
On Mon, Jul 28, 2025 at 4:35 PM Bruce Momjian wrote:
> On Mon, Jul 28, 2025 at 04:24:14PM -0700, Daniel Bauman wrote:
> > Here's where I think the logging is happening.
> https://github.com/postgres/
> > postgres/blob/mas
-Daniel
On Mon, Jul 28, 2025 at 11:38 AM Bruce Momjian wrote:
> On Fri, Jul 25, 2025 at 03:24:48PM -0700, Daniel Bauman wrote:
> > Hey pgsql hackers
> > This is my first email to this list. I'm reaching out about a possible
> doc
> > update for the log_statement pa
Hey pgsql hackers
This is my first email to this list. I'm reaching out about a possible doc
update for the log_statement parameter.
Here's the current doc -
https://www.postgresql.org/docs/current/runtime-config-logging.html
The doc already has a Note bubble for the log_statement parameter with so
