Re: BUG #17543: CSVLOG malformed from disk space error

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "nathanfballance(at)gmail(dot)com" <nathanfballance(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17543: CSVLOG malformed from disk space error
Date: 2022-07-13 00:26:13
Message-ID: Ys4RJVdGew7XBLY2@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jul 11, 2022 at 05:31:35AM -0700, David G. Johnston wrote:
> This list is for reporting bugs, not feature requests.
>
> I’d have to say that there is little interest in sacrificing performance
> for safety here, which seems like an unavoidable proposition.

I'd be curious to hear about an actual proposal if there are things
that could be improved. Saying that, after playing with this area in
the last couple of months to add support for the JSON format, the
design of the syslogger with its set of synced pipes to ensure the
ordering of the logs sent by the backends to the syslogger process
relies on many assumptions, and it may be hard to make things more
reliable without sacrificing performance. Aka, this can already
become a bottleneck with short logs and a rather high logging level
used and we don't want to make that worse.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2022-07-13 00:48:53 Re: BUG #17543: CSVLOG malformed from disk space error
Previous Message Tom Lane 2022-07-12 22:15:54 Re: BUG #17548: Aggregate queries on partitioned tables can cause OOM.