Re: BUG #17543: CSVLOG malformed from disk space error - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #17543: CSVLOG malformed from disk space error
Date
Msg-id CAKFQuwZ5QQM0wQ27avgcVbtkY6YRQbgWCoZnA5kUN8989XWEgQ@mail.gmail.com
Whole thread Raw
In response to BUG #17543: CSVLOG malformed from disk space error  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17543: CSVLOG malformed from disk space error  (Michael Paquier <michael@paquier.xyz>)
Re: BUG #17543: CSVLOG malformed from disk space error  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On Saturday, July 9, 2022, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17543
Logged by:          Nathan Ballance
Email address:      nathanfballance@gmail.com
PostgreSQL version: 14.4
Operating system:   Linux/UNIX
Description:       

Postgresql server with csvlog log_destination enabled will have malformed
CSV upon a disk space error. This causes any loading of the malformed *.csv
log file to error


ASK: Can the CSV file be written to in a safer way which ensures proper
format even upon disk error?


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.

David J.

pgsql-bugs by date:

Previous
From: Jiří Ledvinka
Date:
Subject: RE: server closed the connection unexpectedly - bug report
Next
From: Pavel Borisov
Date:
Subject: Re: BUG #17542: tsquery returns incorrect results with nested, conjuncted followed-by operators