Re: pg_resetwal: Fix wrong directory in log output

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: "zhang_tian_chen(at)163(dot)com" <zhang_tian_chen(at)163(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_resetwal: Fix wrong directory in log output
Date: 2026-02-03 02:13:53
Message-ID: 1BEA161A-B1DC-494C-B235-A47FEE1D7B68@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Feb 3, 2026, at 09:58, zhang_tian_chen(at)163(dot)com wrote:
>
> Hi hackers,
>
> There is a misuse of macro when we output directory information in KillExistingWALSummaries(), pg_resetwal.c. Which should be WALSUMMARYDIR instead of ARCHSTATDIR.
>
> Best regards,
> Tianchen Zhang<v1-0001-Fix-incorrect-directory-macro-in-KillExistingWALS.patch>

Indeed a bug. Looking at the code:

```
/*
* Remove existing WAL summary files
*/
static void
KillExistingWALSummaries(void)
{
DIR *xldir;

xldir = opendir(WALSUMMARYDIR);
if (xldir == NULL)
pg_fatal("could not open directory \"%s\": %m", WALSUMMARYDIR);
...

if (errno)
pg_fatal("could not read directory \"%s\": %m", WALSUMMARYDIR);

if (closedir(xldir))
pg_fatal("could not close directory \"%s\": %m", ARCHSTATDIR); <<=== It should really be WALSUMMARYDIR
}
```

I guess closedir() is hard to fail, that’s why the problem has not been noticed earlier.

The patch is straightforward and looks correct.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-02-03 02:15:35 Re: pg_dumpall --roles-only interact with other options
Previous Message Michael Paquier 2026-02-03 02:04:48 Re: pg_resetwal: Fix wrong directory in log output