| From: | "Edward J(dot) Sabol" <edwardjsabol(at)gmail(dot)com> |
|---|---|
| To: | Jef Mortelle <jefmortelle(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Upgrade from PG12 to PG |
| Date: | 2023-07-20 13:29:25 |
| Message-ID: | 02E1F4FD-C346-4169-86F5-2CB17232D838@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Jul 20, 2023, at 7:23 AM, Jef Mortelle <jefmortelle(at)gmail(dot)com> wrote:
> I use /usr/lib/postgresql15/bin/pg_upgrade -v -p 5431 -P 5432
>
> I takes a lot of time, more than 6 hours
I'm in the middle of a similar database migration myself, but I'm coming from 10.23.
Have you considered adding the --link and --jobs=NN (where NN is the number of CPU cores on your server minus 2 or something like that) to your pg_upgrade command? I wonder if that would speed things up significantly.
Also, if your file system supports reflinks (Linux kernel 4.5 and XFS with reflink support activated or Btrfs or macOS APFS), then use --clone instead of --link.
Good luck,
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jef Mortelle | 2023-07-20 13:42:37 | Re: Upgrade from PG12 to PG |
| Previous Message | Ron | 2023-07-20 13:26:39 | Re: How to schedule long running SQL job |