Re: WAL Insertion Lock Improvements
От
Michael Paquier
Тема
Re: WAL Insertion Lock Improvements
Дата
Msg-id
ZFnnWRqn4PJegIyJ@paquier.xyz
Ответ на
Re: WAL Insertion Lock Improvements (Michael Paquier)
Список
Дерево обсуждения
Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish() Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish() Andres Freund <andres@anarazel.de>
Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish() Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish() Andres Freund <andres@anarazel.de>
WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish()) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish()) Nathan Bossart <nathandbossart@gmail.com>
Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish()) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish()) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Nathan Bossart <nathandbossart@gmail.com>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Nathan Bossart <nathandbossart@gmail.com>
回复: WAL Insertion Lock Improvements adherent postgres <adherent_postgres@hotmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Nathan Bossart <nathandbossart@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Andres Freund <andres@anarazel.de>
Re: WAL Insertion Lock Improvements Andres Freund <andres@anarazel.de>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Andres Freund <andres@anarazel.de>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Andres Freund <andres@anarazel.de>
Re: WAL Insertion Lock Improvements Andres Freund <andres@anarazel.de>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Nathan Bossart <nathandbossart@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
Re: WAL Insertion Lock Improvements Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: WAL Insertion Lock Improvements Michael Paquier <michael@paquier.xyz>
On Tue, May 09, 2023 at 02:10:20PM +0900, Michael Paquier wrote: > Should we split this patch into two parts, as they aim at tackling two > different cases then? One for LWLockConflictsWithVar() and > LWLockReleaseClearVar() which are the straight-forward pieces > (using one pg_atomic_write_u64() in LWLockUpdateVar instead), then > a second for LWLockUpdateVar()? I have been studying that a bit more, and I'd like to take this suggestion back. Apologies for the noise. -- Michael
В списке pgsql-hackers по дате отправления
От: Amit Kapila
Дата: