From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Strange "permission denied" errors on pg_restore |
Date: | 2024-06-29 05:18:55 |
Message-ID: | CANzqJaBDNN9r=uK3jKtmGCCo2k55fJXK9n6CAhL5WN8pa_0pLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Jun 29, 2024 at 1:13 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Sat, 2024-06-29 at 01:04 -0400, Ron Johnson wrote:
> > On Sat, Jun 29, 2024 at 12:31 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
> > > On Fri, 2024-06-28 at 09:34 -0400, Ron Johnson wrote:
> > > > pg_restore: error: COPY failed for table "batch_rp4_y2022m08":
> ERROR: permission denied for schema tapschema
> > >
> > > - Was the database you restored into totally empty?
> > >
> > > - What was the exact "pg_restore" command line?
> >
> > pg_restore -v --clean --create -Fd -j6 --dbname=postgres tap &>
> tap_restore.log
>
> So the database was clean (newly created).
>
> You should perform the restore as a superuser or as a user that has all
> the required permissions. Restoring with a non-superuser can be tricky.
>
I do everything database-related as user "postgres". Only "sudo yum" is
run from my personal account.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-06-29 14:54:05 | Re: Strange "permission denied" errors on pg_restore |
Previous Message | Laurenz Albe | 2024-06-29 05:13:21 | Re: Strange "permission denied" errors on pg_restore |