Re: Pg_restore

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Pg_restore
Date: 2019-03-01 08:38:23
Message-ID: 87ef830f-58e8-487b-d548-7d041aca685d@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/1/19 2:17 AM, Nicola Contu wrote:
> Hello,
> we are trying to move our postgres 10.5 instance to 11.2
>
> We are trying to restore a DB in a pre-production env but we get an error
> on the pg_restore command
>
> [root(at)STAGING]#  /usr/local/pgsql11.2/bin/pg_restore -v -U postgres -L
> /data/cofinder_restore.lst  -d cofinder  -j 16  /home/ncontu/data/dbbackups/C
> pg_restore: connecting to database for restore
> pg_restore: processing item 3098 ENCODING ENCODING
> pg_restore: processing item 3099 STDSTRINGS STDSTRINGS
> pg_restore: processing item 3100 SEARCHPATH SEARCHPATH
> pg_restore: processing item 3101 DATABASE cofinder
> pg_restore: processing item 3 SCHEMA public
> pg_restore: creating SCHEMA "public"
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA
> public postgres
> pg_restore: [archiver (db)] could not execute query: ERROR:  schema
> "public" already exists
>     Command was: CREATE SCHEMA public;
>
> The dump is taken with pgsql10 binaries.
>
> Can you help on this please?
> We also have another DB, but with the other one no issues doing the same
> thing.

Out of curiosity, why are you using the "-L" option instead of restoring the
whole database?

--
Angular momentum makes the world go 'round.

In response to

  • Pg_restore at 2019-03-01 08:17:57 from Nicola Contu

Browse pgsql-general by date

  From Date Subject
Next Message Nicola Contu 2019-03-01 08:45:28 Re: Pg_restore
Previous Message Nicola Contu 2019-03-01 08:17:57 Pg_restore