From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Strange "permission denied" errors on pg_restore |
Date: | 2024-06-29 05:13:21 |
Message-ID: | 42d837098e471906e23ed5ef345a1172145c76da.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-06-29 05:18:55 | Re: Strange "permission denied" errors on pg_restore |
Previous Message | Ron Johnson | 2024-06-29 05:04:22 | Re: Strange "permission denied" errors on pg_restore |