Re: basic_archive lost archive_directory

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Олег Самойлов <splarv(at)ya(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: basic_archive lost archive_directory
Date: 2026-02-06 14:25:25
Message-ID: 1317421770387925@cea5cfd9-50d3-4d85-a924-a7cc75f8f215
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello

How to reproduce:

1) configure

archive_mode = on
archive_library = 'basic_archive'
basic_archive.archive_directory = '/some/path/'

2) start postgres and verify archive works
3) make this directory temporary inaccessible. NFS will give you many ways to achieve this, here just mv /some/ /some_moved/ is enough.
4) basic_archive will complain ERROR: could not create file ... No such file or directory for new WAL archive attempts
5) restart archiver process with any reason: kill it or restart postgres
6) make archive_directory accessible again: archiver process will not check the directory's existence again and continue to complain about unconfigured archive_directory

Maybe it makes sense to move the directory existence check from check_archive_directory (guc check callback) to basic_archive_configured? (attached)

regards, Sergei

Attachment Content-Type Size
basic_archive_move_is_dir.patch text/x-diff 1.7 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2026-02-06 16:52:01 Re: BUG #19395: Postgres master: undeclared function 'typeof_unqual'
Previous Message Олег Самойлов 2026-02-06 13:02:48 Re: basic_archive lost archive_directory