On 17 August 2017 at 01:20, Heikki Linnakangas <hlinn...@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 -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers