pg_restore man page (version 9.4) > -d/dbname clarification request

On 6/15/17 00:00, Charles wrote:

Please consider changing "Connect to database dbname and restore
directly into the database" to "Connect to database dbname and restore
directly into the database named in the input file"

But that's not what it does.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

On 15/06/17 20:48, Peter Eisentraut wrote:

On 6/15/17 00:00, Charles wrote:

Please consider changing "Connect to database dbname and restore
directly into the database" to "Connect to database dbname and restore
directly into the database named in the input file"

But that's not what it does.

Thank you Peter

I am new to postgres so can easily be wrong.

The suggestion was based on how pg_restore behaved when used this way
(as user postgres on a Debian Jessie server):

$ dropdb redmine_default
$ pg_restore --create --dbname=postgres
redmine_default-2017-06-11@18\:21\:06.sql

The .sql file had been created on another server using:

pg_dump --format=custom --lock-wait-timeout=6000000 --username=postgres
--no-password redmine_default

After running the pg_restore command the redmine_default was populated.

Given that database redmine_default was not named on the pg_restore
command I concluded that its name must have been found in the .sql file.

Best, Charles

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

On 6/16/17 01:09, Charles wrote:

The suggestion was based on how pg_restore behaved when used this way
(as user postgres on a Debian Jessie server):

$ dropdb redmine_default
$ pg_restore --create --dbname=postgres
redmine_default-2017-06-11@18\:21\:06.sql

If you are using the --create option, you get a different behavior.
This is pretty explicitly described on the pg_restore man page under
--describe.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

On 6/16/17 10:15, Peter Eisentraut wrote:

On 6/16/17 01:09, Charles wrote:

The suggestion was based on how pg_restore behaved when used this way
(as user postgres on a Debian Jessie server):

$ dropdb redmine_default
$ pg_restore --create --dbname=postgres
redmine_default-2017-06-11@18\:21\:06.sql

If you are using the --create option, you get a different behavior.
This is pretty explicitly described on the pg_restore man page under
--describe.

I mean under --create.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs