| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Jason Ralph <jralph(at)affinitysolutions(dot)com> |
| Cc: | Pankaj Jangid <pankaj(dot)jangid(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG11 Parallel Thanks!! |
| Date: | 2019-10-04 18:28:50 |
| Message-ID: | CAH2-Wz=yttoPzyxg7aDZ8uu8NXizwy4tyDu8nTiTOvUugnGfyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 3, 2019 at 10:31 AM Jason Ralph
<jralph(at)affinitysolutions(dot)com> wrote:
> The end of month process that we run at my company was a pg_dump and pg_restore of 3 tables, these tables are around ~(400GB) each. The entire process on pg93 took 29 hours.
>
> The index creation portion of the restore on the target pg9.3 database took:
> 5) time: -15 hours -4 minute ((-54264 % 60)) seconds
>
> The index creation of the restore on the target db after pg11 upgrade on source and target took:
> 5) time: -5 hours -7 minute ((-18434 % 60)) seconds
>
> We saved 10 hours!!
The sort code received many improvements over the years, really
starting in 9.5, and continuing in 9.6, 10 and 11. FWIW, I think that
that was probably the biggest factor here. Though parallel CREATE
INDEX will have helped as well.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-10-04 19:14:53 | Re: Pg11 -- MultiXactId xxxx has not been created yet -- apparent wraparound |
| Previous Message | Tom Lane | 2019-10-04 17:36:03 | Re: Postgres 12: backend crashes when creating non-deterministic collation |