Horton

Re: pgsql: Fix and document lock handling for in-memory replication slot da

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, pgsql-committers@lists.postgresql.org
Date: 2018-06-11T21:47:27Z
Lists: pgsql-hackers 
On Mon, Jun 11, 2018 at 09:49:52AM -0700, Andres Freund wrote:
> Same is true for the codepaths calling GetRedoRecPtr().

You are right.  I'll fix in a minute.  A first commit's stress make
things really harder to get right...

> I don't object to the general idea of adding locking - although the
> benefit are nearly guaranteed to be cosmetic - but this has the
> potential to make things worse.

Thanks.
--
Michael

Commits

  1. Fix oversight from 9e149c8 with spin-lock handling

  2. Fix and document lock handling for in-memory replication slot data