Re: vacuumdb idle processes
| От | Jeff Janes |
|---|---|
| Тема | Re: vacuumdb idle processes |
| Дата | |
| Msg-id | CAMkU=1x8Uv1TdXy_RFtAtjHoGB7suQRy0_BvDThrNwo3-Y8hOA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: vacuumdb idle processes (Nikhil Shetty <nikhil.dba04@gmail.com>) |
| Ответы |
Re: vacuumdb idle processes
Re: vacuumdb idle processes |
| Список | pgsql-admin |
On Sun, Jun 13, 2021 at 8:43 AM Nikhil Shetty <nikhil.dba04@gmail.com> wrote:
Hi,I tested this scenario and it seems if vacuumdb is started with multiple jobs and one of the jobs doesn't complete due to a lock or whatever reason, other jobs will stay idle and don't release the connection until the stuck job is finished.For my understanding, why do we need this behaviour?
I don't think we **need** this behavior, it is just a simple way to wait for each one to finish and then close it; waiting for each specific one in the order it is present in the list. Is there an important reason we need a more complex behavior, closing each one as soon as it becomes idle once the work queue is empty?
Cheers,
Jeff
В списке pgsql-admin по дате отправления: