| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julie Nishimura <juliezain(at)hotmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: upgrade and migrate |
| Date: | 2019-12-04 04:48:43 |
| Message-ID: | 20191204044843.GD2381@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 03, 2019 at 10:32:22PM +0000, Julie Nishimura wrote:
> Hello, what is the best way to migrate from PostgreSQL 8.3.11 on
> x86_64-redhat-linux-gnu to PostgreSQL 9.6.16 on x86_64-pc-linux-gnu
> server, with minimal downtime?
> The caveat is the source has about 80 databases overall almost 30
> TB. I could migrate the smallest ones (up to 1 tb) using pg_dump and
> pg_restore, but the largest hot database is almost 17 tb, and I am
> not sure how to approach this effort in a better and efficient way?
pg_upgrade could be one way to go here. That's not the scale pg_dump
would be very good at. I would have personally avoided using pg_dump
above 10~20GB. Depending on the downtime you are ready to accept,
a migration based on Slony could be something to investigate.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2019-12-04 07:13:26 | Re: upgrade and migrate |
| Previous Message | Stephen Frost | 2019-12-04 03:09:07 | Re: pg_basebackup + incremental base backups |