From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Backup and Restore (pg_dump & pg_restore) |
Date: | 2019-04-21 19:25:51 |
Message-ID: | 16449.1555874751@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 4/21/19 9:35 AM, Daulat Ram wrote:
>> pg_restore: [archiver (db)] could not execute query: ERROR: schema
>> "public" already exists
>> Command was: CREATE SCHEMA public;
> Expected as the public schema is there by default. It is an
> informational error, you can ignore it.
It's expected only if you made a dump file with 9.6's pg_dump and
restored it with a later pg_restore; there were some changes in
how the public schema got handled between the two versions.
The usual recommendation when you are doing a version migration
is to use the newer release's pg_dump to suck the data out of
the older server. If you can't do that, it'll (probably)
still work, but you may have cosmetic issues like this one.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Susan Hurst | 2019-04-21 19:33:16 | Display View Columns and Their Source Tables and Columns |
Previous Message | Adrian Klaver | 2019-04-21 18:46:09 | Re: Backup and Restore (pg_dump & pg_restore) |
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-04-21 20:42:06 | Re: Backup and Restore (pg_dump & pg_restore) |
Previous Message | Adrian Klaver | 2019-04-21 18:46:09 | Re: Backup and Restore (pg_dump & pg_restore) |