From: Tom Lane <tgl@sss.pgh.pa.us>
To: Johan Antonissen <windhoos@gmail.com>
cc: pgsql-novice@lists.postgresql.org
Subject: Re: 
In-reply-to: 
 <CAEac0YaJuyWc=7Rc6kWf6hEphD-s76Ge2Q01hiAo_7rtS1YJ6w@mail.gmail.com>
References: 
 <CAEac0YaJuyWc=7Rc6kWf6hEphD-s76Ge2Q01hiAo_7rtS1YJ6w@mail.gmail.com>
Comments: In-reply-to Johan Antonissen <windhoos@gmail.com>
	message dated "Mon, 17 Apr 2023 09:31:59 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2416656.1681739651.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Apr 2023 09:54:11 -0400
Message-ID: <2416657.1681739651@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2416657.1681739651%40sss.pgh.pa.us>
Precedence: bulk

Johan Antonissen <windhoos@gmail.com> writes:
> However when I try to deploy django and connect to my postgres server
> postgres gives me a permission error:

> python manage.py sqlcreate | sudo -u postgres psql -U postgres

> results to:

> Could not change directory ... permission deniedCREATE ROLECREATE DATABA=
SEGRANT

The "Could not change directory ... permission denied" part is mostly
cosmetic.  It happens when psql is invoked in a current working
directory that the postgres user can't read.  The fact that you're
getting "CREATE ROLE", "CREATE DATABASE", etc command completion
acknowledgements indicates that the SQL script is executing
successfully anyway.  So what you've showed us doesn't really
indicate that anything is wrong; although you could try it from
a publicly-readable starting directory if you want to be sure.

			regards, tom lane