Re: Postgres12 - Confusion with pg_restore
От | Laura Smith |
---|---|
Тема | Re: Postgres12 - Confusion with pg_restore |
Дата | |
Msg-id | egzaXsylaym1oO3-sXNZ3BRbUMWopcTQRN7MFkX6JYMZYPCchBgiFbmNufntm0QBKIaRxGlG56-Da5kU1u4-d9fjC8hdnXY22KVRLemH7m4=@protonmail.ch обсуждение исходный текст |
Ответ на | Re: Postgres12 - Confusion with pg_restore (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 5 June 2020 19:35, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Laura Smith n5d9xq3ti233xiyif2vp@protonmail.ch writes: > > > But doesn't the second half of my original post demonstrate that I tried that very thing ? I did try creating the databasefirst, 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 > Thanks for the clarificaiton Tom. All working now !
В списке pgsql-general по дате отправления: