RE: Shortest offline window on database migration

From: Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com>
To: Haroldo Kerry <hkerry(at)callix(dot)com(dot)br>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: RE: Shortest offline window on database migration
Date: 2019-05-30 15:54:52
Message-ID: E9FA92C2921F31408041863B74EE4C2001BD6F949F@ccpmaildag02.cantab.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>Has anyone been through this type of problem?
>

You could set up a new, empty db (with checksums enabled, etc.) on the new hardware and then use logical replication to sync across all the data from the existing cluster.
(This logical replica could be doing binary replication to hot standbys too, if you like).

When the sync has finished you could perhaps gradually shift read-only load over to the new db, and finally switch write load too - your downtime would then be limited to how long this final cut-over takes.

Steve.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Haroldo Kerry 2019-05-30 16:23:33 Re: Shortest offline window on database migration
Previous Message Tomas Vondra 2019-05-30 15:31:28 Re: Shortest offline window on database migration