Re: Misleading/inaccurate error message from pg_basebackup - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: Misleading/inaccurate error message from pg_basebackup
Date
Msg-id A82133F3-968A-427A-953A-3A5B37ABAA65@yesql.se
Whole thread Raw
In response to Misleading/inaccurate error message from pg_basebackup  (c@osss.net)
Responses Re: Misleading/inaccurate error message from pg_basebackup  (Casey <c@osss.net>)
List pgsql-bugs
> On 22 Jan 2024, at 17:47, c@osss.net wrote:

> pg_basebackup can throw an error which is inaccurate and misleading:

> $ pg_basebackup --version
> Error: /var/lib/postgresql/14/main is not accessible; please fix the directory permissions (/var/lib/postgresql/14/
shouldbe world readable) 
>
> In fact it does not need to be world readable at all - the subdirectory just needs to be created:

> This check is being done in cases where it's unnecessary, as it shouldn't matter at all when running a simple
--versionor --help, anyways. 

There is no such check before --version or --help, and no such check at all in
pg_basebackup.  Whatever is raising that error probably isn't postgres or
pg_basebackup.  When pg_basebackup logs an error it looks like this:

pg_basebackup: error: /var/lib/postgresql/14/main is not accessible

Something else is doing this on your system.

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit
Next
From: Richard Guo
Date:
Subject: Re: BUG #18305: Unexpected error: "WindowFunc not found in subplan target lists" triggered by subqueries