Re: global / super barriers (for checksums) - Mailing list pgsql-hackers

From Andres Freund
Subject Re: global / super barriers (for checksums)
Date
Msg-id 20181227132255.temuxuukwetiak3g@alap3.anarazel.de
Whole thread Raw
In response to Re: global / super barriers (for checksums)  (Magnus Hagander <magnus@hagander.net>)
Responses Re: global / super barriers (for checksums)  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Hi,

On 2018-12-27 13:54:34 +0100, Magnus Hagander wrote:
> Finally getting around to playing with this one and it unfortunately
> doesn't apply anymore (0003).
> 
> I think it's just a matter of adding those two rows though, right? That is,
> it's not an actual conflict it's just something else added in the same
> place?

What do you mean with "rows" here? I see a bunch of trivial conflicts
due to changes in atomics initialization but nothing else?  And yes, I'd
not expect any meaningful conflicts.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writablevariables)
Next
From: Alvaro Herrera
Date:
Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace onthe fly