From: Tom Lane <tgl@sss.pgh.pa.us>
To: arasopero.1@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18054: Permission denied.
In-reply-to: <18054-792b6eaac27319ad@postgresql.org>
References: <18054-792b6eaac27319ad@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 13 Aug 2023 04:26:48 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <791479.1691983639.1@sss.pgh.pa.us>
Date: Sun, 13 Aug 2023 23:27:19 -0400
Message-ID: <791480.1691983639@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/791480.1691983639%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I can not make backup and restoration of my db by this issues:
> baap@baap-notebookpc:~$ sudo su postgres
> [sudo] password for baap: 
> postgres@baap-notebookpc:/home/baap$ psql
> could not change directory to "/home/baap": Permission denied
> psql (15.4 (Ubuntu 15.4-1.pgdg22.04+1))

You have not shown an actual failure here.  The "could not change
directory" warning might be alarming, but you have not explained
how it causes you any problem.

What is actually happening, I think, is that psql is chdir'ing
to someplace else in pursuit of figuring out its own absolute
path, and then it tries to chdir back to where it was started
from, and fails because that directory is not readable by the
postgres user.  It produces a warning about that but continues
anyway.  So this doesn't affect your ability to use SQL
commands, but it might affect your ability to run meta-commands
that expect the current working directory to be "/home/baap".
However, given that psql could not read any files within that
directory, it's not clear to me what practical problem ensues
that wouldn't manifest in some other form anyway.

			regards, tom lane