From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgres12 - Confusion with pg_restore |
Date: | 2020-06-05 18:35:26 |
Message-ID: | 1511852.1591382126@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> writes:
> But doesn't the second half of my original post demonstrate that I tried that very thing ? I did try creating the database first, but pg_restore just complained even more ?
There are two ways you can do this:
1. Create the new database by hand (with CREATE DATABASE) and tell
pg_restore to restore into it. In this case you *don't* say -C
to pg_restore, and your -d switch points at the DB to restore into.
2. Have pg_restore issue CREATE DATABASE. In this case you *do* use
the -C switch, and your -d switch has to point at some pre-existing
database that pg_restore can connect to for long enough to issue the
CREATE DATABASE.
You can't mix-and-match these approaches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Paul van der Linden | 2020-06-05 18:39:17 | Re: Possible improvement |
Previous Message | Laura Smith | 2020-06-05 18:27:11 | Re: Postgres12 - Confusion with pg_restore |