From: | Vigneshk Kvignesh <krrvignesh2(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: PG11 to PG14 Migration Slowness |
Date: | 2023-01-27 11:57:40 |
Message-ID: | CABQmCUkb6mbEbqr3ro3tunvpdCiKA1Anc2kvOU_z7JDJgNXM3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Sorry for the delayed response. We have an fdw extension, we started code
changes in the extension for PGv14 on 14.3, we just completed code changes,
testing and benchmarking. We'll retarget to 14.6
Also we'll take a look at the changes for pg_dump in v15 . Thanks for the
advice.
Thanks and Regards,
Vignesh K.
On Thu, 12 Jan 2023 at 21:18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Vigneshk Kvignesh <krrvignesh2(at)gmail(dot)com> writes:
> > I'm migrating our existing PG instances from PG11.4 to PG14.3. I
> > have around 5 Million Tables in a single database. When migrating using
> > pg_upgrade, its taking 3 hours for the process to complete. I'm not sure
> if
> > its the intended behaviour or we're missing something here.
>
> There was some work done in v15 to make pg_dump deal better with
> zillions of tables. Don't know if you can consider retargeting
> to v15, or how much the speedups would help in your particular
> situation.
>
> Why are you using 14.3, when the current release is 14.6?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Drouvot, Bertrand | 2023-01-27 12:09:16 | Re: Minimal logical decoding on standbys |
Previous Message | Amit Kapila | 2023-01-27 11:54:54 | Re: Logical replication timeout problem |