| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Jason Long <hack3rcon(at)yahoo(dot)com> |
| Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Guard |
| Date: | 2024-02-28 14:12:44 |
| Message-ID: | CAKAnmmLpQSG7XSHiGG7eJvoy7TT8+qO39nVmMNOvO3GYekzw=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 27, 2024 at 3:48 PM Jason Long <hack3rcon(at)yahoo(dot)com> wrote:
> Suppose you want to transfer the database of a website like Amazon.com to
> a new server and delete the old one. Many users are buying and selling on
> this website at the same time and it is not possible to turn off the
> server. What do you do to move a database to another server?
>
If we assume your question is "how can we migrate to a new system while
keeping the old one up and running to minimize downtime?" the answer is
logical replication.
https://www.crunchydata.com/blog/data-to-go-postgres-logical-replication
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-02-28 14:30:01 | Re: Orphan table files at data/base/ |
| Previous Message | Riivo Kolka | 2024-02-28 13:44:47 | Orphan table files at data/base/ |