From: | Josh Innis <joshinnis(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Johan Antonissen <windhoos(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
Subject: | Re: |
Date: | 2023-04-17 15:46:34 |
Message-ID: | CAAZtsUqeyYTKy8S0DNJxagAC5=rivUdiWTGsYUkni5eRYhjeHw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
+1
On Mon, Apr 17, 2023 at 10:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Johan Antonissen <windhoos(at)gmail(dot)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
> DATABASEGRANT
>
> 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
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Johan Antonissen | 2023-04-17 18:06:43 | Re: |
Previous Message | Tom Lane | 2023-04-17 13:54:11 | Re: |