Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish())

Поиск
Список
Период
Сортировка
Искать
От
Nathan Bossart
Тема
Re: WAL Insertion Lock Improvements (was: Re: Avoid LWLockWaitForVar() for currently held WAL insertion lock in WaitXLogInsertionsToFinish())
Дата
Msg-id
20221203003158.GA2518778@nathanxps13
Ответ на
Список
Дерево обсуждения
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 Fri, Dec 02, 2022 at 04:32:38PM +0530, Bharath Rupireddy wrote:
> On Fri, Dec 2, 2022 at 6:10 AM Andres Freund  wrote:
>> I'm not sure this is quite right - don't we need a memory barrier. But I don't
>> see a reason to not just leave this code as-is. I think this should be
>> optimized entirely in lwlock.c
> 
> Actually, we don't need that at all as LWLockWaitForVar() will return
> immediately if the lock is free. So, I removed it.

I briefly looked at the latest patch set, and I'm curious how this change
avoids introducing memory ordering bugs.  Perhaps I am missing something
obvious.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com


В списке pgsql-hackers по дате отправления
От: David Zhang
Дата:
Сообщение: Re: Patch: Global Unique Index
От: Nathan Bossart
Дата:
FAQ