Re: [HACKERS] Atomics for heap_parallelscan_nextpage() - Mailing list pgsql-hackers

From David Rowley
Subject Re: [HACKERS] Atomics for heap_parallelscan_nextpage()
Date
Msg-id CAKJS1f95f=6L7sbWLexJ7nJEKcvXoM_GTTvv4KBGCCJR7haZ+Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Atomics for heap_parallelscan_nextpage()  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On 17 August 2017 at 01:20, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> Looks reasonable. I edited the comments and the variable names a bit, to my
> liking, and committed. Thanks!

Thanks for committing. I've just been catching up on all that went on
while I was sleeping. Thanks for handling the cleanup too.

I'll feel better once pademelon goes green again. From looking at the
latest failure on it, it appears that your swapping of
pg_atomic_write_u64 for pg_atomic_init_u64 should fix this. My
apologies for that mistake.

-- David Rowley                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] [BUGS] Replication to Postgres 10 on Windows isbroken
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Function to move the position of a replication slot