Re: pg_restore 12 "permission denied for schema" errors
От | Ron |
---|---|
Тема | Re: pg_restore 12 "permission denied for schema" errors |
Дата | |
Msg-id | 612cf1c4-1f2d-f068-d6cf-54b98bbeb646@gmail.com обсуждение исходный текст |
Ответ на | Re: pg_restore 12 "permission denied for schema" errors (Adrian Klaver <adrian.klaver@aklaver.com>) |
Ответы |
Re: pg_restore 12 "permission denied for schema" errors
Re: pg_restore 12 "permission denied for schema" errors |
Список | pgsql-general |
On 10/20/22 10:02, Adrian Klaver wrote: > On 10/20/22 06:20, Ron wrote: >> On 10/20/22 00:12, Tom Lane wrote: >>> Frank Gard <frank.von.postgresql.org@familie-gard.de> writes: >>>> Am 20.10.22 um 02:58 schrieb Ron: >>>>> pg_restore -v --create --clean --jobs=`nproc` -Fd --dbname=template1 $DB >>>> What database do you want to restore your data into? As far as I know >>>> your pg_restore command would import the data into template1, right? >>> No --- my ears went up about that too, but he's using --create. >>> So template1 is just the springboard for the initial connection >>> in which CREATE DATABASE will be issued. >>> >>> My guess is that there's something inconsistent between source >>> and target installations about roles and role-privilege grants. >>> We don't have enough details to do more than guess, though. >> >> I ran "pg_dumpall --globals-only --no-role-passwords" on the source >> instance, and applied it to the new instance before doing the pg_restore. >> If I hadn't done that, pg_restore would have thrown errors on all the >> GRANT and ALTER TABLE ... OWNER TO statements embedded in the backup. >> > > Some questions: > > 1) The backup was from a Postgres 12.x database using a version 12 or > higher instance of pg_backup? pg_dump and pg_restore are 12.11 from RHEL8. > 3) What if you run without --jobs? It runs without error. Add "--jobs=2" and the errors appear. -- Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: