RE: releasing ParallelApplyTxnHash when pa_launch_parallel_worker returns NULL

Поиск
Список
Период
Сортировка
От houzj.fnst@fujitsu.com
Тема RE: releasing ParallelApplyTxnHash when pa_launch_parallel_worker returns NULL
Дата
Msg-id OS0PR01MB5716EECFCEDA36DC126826AF94FC9@OS0PR01MB5716.jpnprd01.prod.outlook.com
обсуждение исходный текст
Ответ на releasing ParallelApplyTxnHash when pa_launch_parallel_worker returns NULL  (Ted Yu <yuzhihong@gmail.com>)
Ответы Re: releasing ParallelApplyTxnHash when pa_launch_parallel_worker returns NULL
Список pgsql-hackers
Дерево обсуждения 
On Wednesday, January 11, 2023 1:25 AM Ted Yu <yuzhihong@gmail.com> wrote:

> I was reading src/backend/replication/logical/applyparallelworker.c .
> In `pa_allocate_worker`, when pa_launch_parallel_worker returns NULL, I think the `ParallelApplyTxnHash` should be
released.

Thanks for reporting.

ParallelApplyTxnHash is used to cache the state of streaming transactions being
applied. There could be multiple streaming transactions being applied in
parallel and their information were already saved in ParallelApplyTxnHash, so
we should not release them just because we don't have a worker available to
handle a new transaction here.

Best Regards,
Hou zj

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Spinlock is missing when updating two_phase of ReplicationSlot
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: [PATCH] Add overlaps geometric operators that ignore point overlaps