Postgres Pro
Downloads
Home   >   mailing lists

Re: Further cleanup of pg_dump/pg_restore item selection code - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Further cleanup of pg_dump/pg_restore item selection code
Date
Msg-id CAKFQuwYp-K+ZjdGnJXTW5HqOugWiWE1UyMmgoKgMy+4mEM4OLw@mail.gmail.com
Whole thread Raw
In response to Re: Further cleanup of pg_dump/pg_restore item selection code  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Further cleanup of pg_dump/pg_restore item selection code
List pgsql-hackers
Tree view
On Wednesday, January 24, 2018, Tom Lane <tgl@sss.pgh.pa.us> wrote:
I think you might be missing one of the main points here, which is
that --create is specified as causing both a CREATE DATABASE and a
reconnect to that database.

I missed the implication though I read and even thought about questioning that aspect (in pg_dump though, not restore).

Should pg_restore fail if asked to --create without a database entry in the TOC?

David J.

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Further cleanup of pg_dump/pg_restore item selection code
Next
From: Masahiko Sawada
Date:
Subject: Re: PATCH: Exclude unlogged tables from base backups