pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_restore man page (version 9.4) > -d/dbname clarification request
5+ messages / 2 participants
[nested] [flat]
* pg_restore man page (version 9.4) > -d/dbname clarification request
@ 2017-06-15 04:00 Charles <c@charlesmatkinson.org>
2017-06-15 15:18 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 5+ messages in thread
From: Charles @ 2017-06-15 04:00 UTC (permalink / raw)
To: pgsql-docs
Hello pgsql-docs :-)
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"
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_restore man page (version 9.4) > -d/dbname clarification request
2017-06-15 04:00 pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
@ 2017-06-15 15:18 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 05:09 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
0 siblings, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2017-06-15 15:18 UTC (permalink / raw)
To: Charles <c@charlesmatkinson.org>; pgsql-docs
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_restore man page (version 9.4) > -d/dbname clarification request
2017-06-15 04:00 pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
2017-06-15 15:18 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
@ 2017-06-16 05:09 ` Charles <c@charlesmatkinson.org>
2017-06-16 14:15 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 5+ messages in thread
From: Charles @ 2017-06-16 05:09 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; 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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_restore man page (version 9.4) > -d/dbname clarification request
2017-06-15 04:00 pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
2017-06-15 15:18 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 05:09 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
@ 2017-06-16 14:15 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 16:42 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 2017-06-16 14:15 UTC (permalink / raw)
To: Charles <c@charlesmatkinson.org>; 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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: pg_restore man page (version 9.4) > -d/dbname clarification request
2017-06-15 04:00 pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
2017-06-15 15:18 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 05:09 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
2017-06-16 14:15 ` Re: pg_restore man page (version 9.4) > -d/dbname clarification request Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
@ 2017-06-16 16:42 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 5+ messages in thread
From: Peter Eisentraut @ 2017-06-16 16:42 UTC (permalink / raw)
To: Charles <c@charlesmatkinson.org>; 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
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2017-06-16 16:42 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-06-15 04:00 pg_restore man page (version 9.4) > -d/dbname clarification request Charles <c@charlesmatkinson.org>
2017-06-15 15:18 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 05:09 ` Charles <c@charlesmatkinson.org>
2017-06-16 14:15 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-06-16 16:42 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox