From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump to a remote server |
Date: | 2018-04-17 04:07:03 |
Message-ID: | 375dee68-48ba-346b-76c3-8dff20309ab7@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/16/2018 06:43 PM, Ron wrote:
>
>
> On 04/16/2018 07:18 PM, Adrian Klaver wrote:
>> On 04/16/2018 04:58 PM, Ron wrote:
>>> We're upgrading from v8.4 to 9.6 on a new VM in a different DC. The
>>> dump file will be more than 1TB, and there's not enough disk space on
>>> the current system for the dump file.
>>>
>>> Thus, how can I send the pg_dump file directly to the new server
>>> while the pg_dump command is running? NFS is one method, but are
>>> there others (netcat, rsync)? Since it's within the same company,
>>> encryption is not required.
>>
>> Maybe?:
>>
>> pg_dump -d test -U postgres -Fc | ssh aklaver(at)arkansas 'cat >
>> test_cat.out'
>
> That looks promising. I could then "pg_restore -jX".
More promising would be the suggestion from Michael Nolan:
"Can you run pg_dump on the new server, connecting remotely to the
current one?"
It eliminates two programs(ssh and cat) and a pipe.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Moench-Tegeder | 2018-04-17 06:00:52 | Re: pg_dump to a remote server |
Previous Message | Keith Fiske | 2018-04-17 03:24:15 | Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade |