Re: optimizing pg_upgrade's once-in-each-database steps - Mailing list pgsql-hackers
Attachment
- v3-0001-introduce-framework-for-parallelizing-pg_upgrade-.patch
- v3-0002-use-new-pg_upgrade-async-API-for-subscription-sta.patch
- v3-0003-move-live_check-variable-to-user_opts.patch
- v3-0004-use-new-pg_upgrade-async-API-for-retrieving-relin.patch
- v3-0005-use-new-pg_upgrade-async-API-to-parallelize-getti.patch
- v3-0006-use-new-pg_upgrade-async-API-to-parallelize-repor.patch
- v3-0007-parallelize-data-type-checks-in-pg_upgrade.patch
pgsql-hackers by date: