Re: Atomic operations within spinlocks

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Atomic operations within spinlocks
Дата
Msg-id 20200604070328.GS89559@paquier.xyz
обсуждение исходный текст
Ответ на Re: Atomic operations within spinlocks  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Thu, Jun 04, 2020 at 09:40:31AM +1200, Thomas Munro wrote:
> Yeah.  It'd be fine to move that after the spinlock release.  Although
> it's really just for informational purposes only, not for any data
> integrity purpose, reading it before the spinlock acquisition would
> theoretically allow it to appear to be (reportedly) behind
> flushedUpto, which would be silly.

Indeed.  This could just be done after the spinlock section.  Sorry
about that.
--
Michael
Вложения

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

Предыдущее
От: Oleksandr Shulgin
Дата:
Сообщение: Re: libpq copy error handling busted
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Read access for pg_monitor to pg_replication_origin_status view