Re: optimizing pg_upgrade's once-in-each-database steps - Mailing list pgsql-hackers
Attachment
- v4-0001-introduce-framework-for-parallelizing-pg_upgrade-.patch
- v4-0002-use-new-pg_upgrade-async-API-for-subscription-sta.patch
- v4-0003-move-live_check-variable-to-user_opts.patch
- v4-0004-use-new-pg_upgrade-async-API-for-retrieving-relin.patch
- v4-0005-use-new-pg_upgrade-async-API-to-parallelize-getti.patch
- v4-0006-use-new-pg_upgrade-async-API-to-parallelize-repor.patch
- v4-0007-parallelize-data-type-checks-in-pg_upgrade.patch
- v4-0008-parallelize-isn-and-int8-passing-mismatch-check-i.patch
- v4-0009-parallelize-user-defined-postfix-ops-check-in-pg_.patch
- v4-0010-parallelize-incompatible-polymorphics-check-in-pg.patch
- v4-0011-parallelize-tables-with-oids-check-in-pg_upgrade.patch
- v4-0012-parallelize-user-defined-encoding-conversions-che.patch
pgsql-hackers by date: