Postgres Pro
Downloads
Home   >   mailing lists

Re: Atomic operations within spinlocks - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Atomic operations within spinlocks
Date
Msg-id 20200604070328.GS89559@paquier.xyz
Whole thread Raw
In response to Re: Atomic operations within spinlocks  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Oleksandr Shulgin
Date:
Subject: Re: libpq copy error handling busted
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view