| From: | Israel Brewster <ijbrewster(at)alaska(dot)edu> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | PostgreSQL Mailing Lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Fastest option to transfer db? |
| Date: | 2021-09-13 21:10:58 |
| Message-ID: | 13A4934D-41D6-42C5-9039-5DFF4A65D657@alaska.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ok, I have logical replication up-and-running (I guess - seemed to simple to be working. Shouldn’t it be complicated, requiring many steps and configuration changes?), maxing out one CPU core on each machine (more or less), and showing network throughput of around 15M. If DU changes are to be believed, it’s transferring data at about 0.8GB/minute, implying something like a 8 hour transfer time.
Of course, since it is replication, it has the benefit that any data that comes in during that 8 hour window should also be replicated, after which the two systems should remain in sync allowing for zero (or nearly so) downtime cutover. Which is nice.
Any gotchas I need to be aware of during this initial transfer window, such as WAL files building up on the source machine?
---
Israel Brewster
Software Engineer
Alaska Volcano Observatory
Geophysical Institute - UAF
2156 Koyukuk Drive
Fairbanks AK 99775-7320
Work: 907-474-5172
cell: 907-328-9145
> On Sep 13, 2021, at 10:10 AM, Michael Lewis <mlewis(at)entrata(dot)com> wrote:
>
> What version of Postgres is the source? Can you make use of logical replication?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gauthier | 2021-09-13 21:37:58 | what is pg_stat_activity.query for idle connections ? |
| Previous Message | Israel Brewster | 2021-09-13 18:49:59 | Re: Fastest option to transfer db? |