On 2021-Jul-31, Bossart, Nathan wrote:
> On 7/30/21, 4:52 PM, "Alvaro Herrera" <alvherre@alvh.no-ip.org> wrote:
> > I noticed that XLogCtl->lastNotifiedSeg is protected by both the
> > info_lck and ArchNotifyLock. I think it it's going to be protected by
> > the lwlock, then we should drop the use of the spinlock.
>
> That seems reasonable to me. This means that the lock is acquired at
> the end of every XLogWrite(),
Uhh, actually that there sounds really bad; it's going to be a serious
contention point.
Another option might be to make it an atomic.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/