Re: [PATCH] Fix error message in RemoveWalSummaryIfOlderThan to indicate file removal failure

From: zengman <zengman(at)halodbtech(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Junwang Zhao <zhjwpku(at)gmail(dot)com>
Subject: Re: [PATCH] Fix error message in RemoveWalSummaryIfOlderThan to indicate file removal failure
Date: 2026-02-02 03:02:39
Message-ID: tencent_1CA40FCC21C1C770712BC089@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Likely so. This one should be backpatched, as the error generated
> could be confusing if faced. That's very unlikely so, still.. I'll
> look at other places in the tree for similar inconsistencies, while on
> it.

Hi Michael,

Thank you for helping to address this! I’ve gone back and reviewed the code, and noticed `OpenWalSummaryFile`:
```
File
OpenWalSummaryFile(WalSummaryFile *ws, bool missing_ok)
{
char path[MAXPGPATH];
File file;

snprintf(path, MAXPGPATH,
XLOGDIR "/summaries/%08X%08X%08X%08X%08X.summary",
ws->tli,
LSN_FORMAT_ARGS(ws->start_lsn),
LSN_FORMAT_ARGS(ws->end_lsn));

file = PathNameOpenFile(path, O_RDONLY);
if (file < 0 && (errno != EEXIST || !missing_ok))
ereport(ERROR,
(errcode_for_file_access(),
errmsg("could not open file \"%s\": %m", path)));

return file;
}
```
I’m thinking of changing `errno != EEXIST` to `errno != ENOENT` here — would you think this adjustment is appropriate?

--
Regards,
Man Zeng

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-02-02 03:16:08 Re: Improve read_local_xlog_page_guts by replacing polling with latch-based waiting
Previous Message Tom Lane 2026-02-02 02:41:07 Re: relkind as an enum