Re: [PATCH]A minor improvement to the error-report in SimpleLruWriteAll()

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: songlong88(at)126(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH]A minor improvement to the error-report in SimpleLruWriteAll()
Date: 2024-06-04 07:44:09
Message-ID: 20240604.164409.1964339778483522274.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Tue, 28 May 2024 20:15:59 +0800 (CST), "Long Song" <songlong88(at)126(dot)com> wrote in
>
> Hi,
> Actually, I still wonder why only the error message
> of the last failure to close the file was recorded.
> For this unusual situation, it is acceptable to
> record all failure information without causing
> too much logging.
> Was it designed that way on purpose?

Note that SlruReportIOError() causes a non-local exit. To me, the
point of the loop seems to be that we want to close every single file,
apart from the failed ones. From that perspective, the patch disrupts
that intended behavior by exiting in the middle of the loop. It seems
we didn't want to bother collecting errors for every failed file in
that part.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2024-06-04 08:39:05 Re: Minor fixes for couple some comments around MERGE RETURNING
Previous Message Peter Eisentraut 2024-06-04 07:26:06 Re: Build with LTO / -flto on macOS