| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | andres(at)anarazel(dot)de |
| Cc: | david(dot)g(dot)johnston(at)gmail(dot)com, nathanfballance(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17543: CSVLOG malformed from disk space error |
| Date: | 2022-07-13 04:09:15 |
| Message-ID: | 20220713.130915.1705049654649862003.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
At Tue, 12 Jul 2022 17:48:53 -0700, Andres Freund <andres(at)anarazel(dot)de> wrote in
> It might be possible to devise a scheme in which we force rotation in cases
> where corruption might have occurred?
It would be cumbersome to generate unique names for new files then let
the server grab the newest file at restart. I'm not sure what happens
if many files are quickly generated due to ENOSPC. (Maybe fills-up the
dirent then moves to another failure mode..)
Considering how often that can happen, I would choose to make the
reader function robust or to fix the file manually..
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2022-07-13 09:16:38 | Re: can't drop table due to reference from orphaned temp function |
| Previous Message | Andres Freund | 2022-07-13 00:48:53 | Re: BUG #17543: CSVLOG malformed from disk space error |