Re: Moving large table between servers: logical replication or postgres_fdw

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Moving large table between servers: logical replication or postgres_fdw
Date: 2018-12-05 06:23:04
Message-ID: d16ef100-7636-a279-1b5d-54f1b61da5e5@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

pg_backup/pg_restore will work, but parallel is pointless on a single
(unpartitioned) table.

On 12/05/2018 12:13 AM, Rene Romero Benavides wrote:
> I tend to believe that a backup (pg_dump) in custom format (-F c) using
> multiple jobs (parallel) -> restore (pg_restore) also with multiple
> concurrent jobs would be better.
>
> Am Di., 4. Dez. 2018 um 21:14 Uhr schrieb Rhys A.D. Stewart
> <rhys(dot)stewart(at)gmail(dot)com <mailto:rhys(dot)stewart(at)gmail(dot)com>>:
>
> Greetings Folks,
>
> I have a relatively large table (100m rows) that I want to move to a
> new box with more resources. The table isn't doing anything...i.e its
> not being updated or read from. Which approach would be faster to move
> the data over:
>
>   a). Use pg_fdw and do "create local_table as select * from
> foreign_table".
>   b). setup logical replication between the two servers.
>
> Regards,
>
> Rhys
> Peace & Love|Live Long & Prosper
>
>

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rob Sargent 2018-12-05 07:07:21 Re: simple division
Previous Message Ron 2018-12-05 06:17:49 Re: Moving large table between servers: logical replication or postgres_fdw