Re: optimizing pg_upgrade's once-in-each-database steps
Nathan Bossart <nathandbossart@gmail.com>
Attachments
On Sun, Aug 04, 2024 at 07:19:57PM +0100, Ilya Gladyshev wrote: > -- End of review -- Thanks for the review. I've attempted to address all your feedback in v8 of the patch set. I think the names could still use some work, but I wanted to get the main structure in place before trying to fix them. > Regarding keeping the connections, the way I envisioned it entailed passing > a list of connections from one check to the next one (or keeping a global > state with connections?). I didn't concretely look at the code to verify > this, so it's just an abstract idea. My main concern with doing something like that is it could require maintaining a huge number of connections when there are many databases. GUCs like max_connections would need to be set accordingly. I'm a little dubious that the gains would be enough to justify it. -- nathan
Commits
-
Introduce framework for parallelizing various pg_upgrade tasks.
- 40e2e5e92b7d 18.0 landed
-
pg_upgrade: Parallelize WITH OIDS check.
- f93f5f7b984e 18.0 landed
-
pg_upgrade: Parallelize contrib/isn check.
- 9db3018cf83b 18.0 landed
-
pg_upgrade: Parallelize data type checks.
- bbf83cab98f2 18.0 landed
-
pg_upgrade: Parallelize encoding conversion check.
- c880cf258864 18.0 landed
-
pg_upgrade: Parallelize incompatible polymorphics check.
- cf2f82a37cc3 18.0 landed
-
pg_upgrade: Parallelize postfix operator check.
- c34eabfbbfd3 18.0 landed
-
pg_upgrade: Parallelize retrieving extension updates.
- 6ab8f27bc716 18.0 landed
-
pg_upgrade: Parallelize retrieving loadable libraries.
- 46cad8b31927 18.0 landed
-
pg_upgrade: Parallelize retrieving relation information.
- 6d3d2e8e541f 18.0 landed
-
pg_upgrade: Parallelize subscription check.
- 7baa36de58bd 18.0 landed
-
pg_upgrade: Move live_check variable to user_opts.
- 4b56bb4ab485 18.0 landed
-
pg_upgrade: run all data type checks per connection
- 347758b12063 17.0 cited