Re: basic_archive lost archive_directory

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Sergei Kornilov <sk@zsrv.org>, Олег Самойлов <splarv@ya.ru>, pgsql-bugs@lists.postgresql.org, Álvaro Herrera <alvherre@kurilemu.de>
Date: 2026-02-09T21:58:01Z
Lists: pgsql-bugs
On Tue, Feb 10, 2026 at 02:46:39AM +0900, Fujii Masao wrote:
> basic_archive is usually loaded only by the archiver via archive_library.
> In that case, errors reported by check_archive_directory() are not logged
> by default, since GUC check hook errors are normally emitted only by
> the postmaster. As a result, misconfigurations (e.g., a non-existent
> archive_directory) may go unnoticed, which is problematic for users.

I don't think this is true.  With default parameters, I see the following
in my logs with a misconfigured archive directory setting:

2026-02-09 15:53:10.372 CST [12803] WARNING:  invalid value for parameter "basic_archive.archive_directory": "/does/not/exist"
2026-02-09 15:53:10.372 CST [12803] DETAIL:  Specified archive directory does not exist.

-- 
nathan



Commits

  1. basic_archive: Allow archive directory to be missing at startup.