Avoid distributing new catalog snapshot again for the transaction being decoded.

Поиск
Список
Период
Сортировка
От houzj.fnst@fujitsu.com
Тема Avoid distributing new catalog snapshot again for the transaction being decoded.
Дата
Msg-id OS0PR01MB57169E394CD4AB71F9C6D58E940E9@OS0PR01MB5716.jpnprd01.prod.outlook.com
обсуждение исходный текст
Ответы Re: Avoid distributing new catalog snapshot again for the transaction being decoded.  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Список pgsql-hackers
Hi,

When doing some other related work, I noticed that when decoding the COMMIT
record via SnapBuildCommitTxn()-> SnapBuildDistributeNewCatalogSnapshot() we
will add a new snapshot to all transactions including the one being decoded(just committed one).

But since we've already done required modifications in the snapshot for the
current transaction being decoded(in SnapBuildCommitTxn()), so I think we can
avoid adding a snapshot for it again.

Here is the patch to improve this.
Thoughts ?

Best regards,
Hou zhijie


Вложения

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

Предыдущее
От: Jakub Wartak
Дата:
Сообщение: Re: CREATE UNLOGGED TABLE seq faults when debug_discard_caches=1
Следующее
От: Maxim Orlov
Дата:
Сообщение: Re: [BUG] FailedAssertion in SnapBuildPurgeOlderTxn