| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "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-11 12:31:35 |
| Message-ID: | CAKFQuwZ5QQM0wQ27avgcVbtkY6YRQbgWCoZnA5kUN8989XWEgQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Saturday, July 9, 2022, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17543
> Logged by: Nathan Ballance
> Email address: nathanfballance(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Borisov | 2022-07-11 12:34:37 | Re: BUG #17542: tsquery returns incorrect results with nested, conjuncted followed-by operators |
| Previous Message | Jiří Ledvinka | 2022-07-11 08:05:53 | RE: server closed the connection unexpectedly - bug report |