Re: Further cleanup of pg_dump/pg_restore item selection code

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Further cleanup of pg_dump/pg_restore item selection code
Date: 2018-01-25 05:24:02
Message-ID: CAKFQuwYp-K+ZjdGnJXTW5HqOugWiWE1UyMmgoKgMy+4mEM4OLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, January 24, 2018, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2018-01-25 05:31:21 Re: PATCH: Exclude unlogged tables from base backups
Previous Message David G. Johnston 2018-01-25 05:19:03 Re: Further cleanup of pg_dump/pg_restore item selection code