Re: optimizing pg_upgrade's once-in-each-database steps
| От | Corey Huinker |
|---|---|
| Тема | Re: optimizing pg_upgrade's once-in-each-database steps |
| Дата | |
| Msg-id | CADkLM=e0KxKJH0XSG6x2oGK7-W2Eet4AwwCqz5pxAG7QthX4Xw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: optimizing pg_upgrade's once-in-each-database steps (Nathan Bossart <nathandbossart@gmail.com>) |
| Ответы |
Re: optimizing pg_upgrade's once-in-each-database steps
|
| Список | pgsql-hackers |
On Tue, Aug 6, 2024 at 3:20 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
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.
I think the underlying mechanism is basically solid, but I have one question: isn't this the ideal case for using libpq pipelining? That would allow subsequent tasks to launch while the main loop slowly gets around to clearing off completed tasks on some other connection.
В списке pgsql-hackers по дате отправления: