| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump to a remote server |
| Date: | 2018-04-17 01:43:34 |
| Message-ID: | c105053c-372c-b258-5a27-ca952e7f063b@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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".
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Fiske | 2018-04-17 03:24:15 | Re: client_encoding issue with SQL_ASCII on 8.3 to 10 upgrade |
| Previous Message | Ron | 2018-04-17 01:41:56 | Re: pg_dump to a remote server |