Re: LogwrtResult contended spinlock - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: LogwrtResult contended spinlock
Date
Msg-id 36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com
Whole thread Raw
In response to Re: LogwrtResult contended spinlock  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: LogwrtResult contended spinlock
List pgsql-hackers
Hello Alvaro and Bharath,

07.04.2024 15:19, Alvaro Herrera wrote:
> I pushed the "copy" pointer now, except that I renamed it to "insert",
> which is what we call the operation being tracked.  I also added some
> comments.

I've discovered that Windows x86 build fails tests after commit f3ff7bf83.
Using "x86 Native Tools Command Prompt for VS 2022", I do:
meson setup build -Dcassert=true
cd build
ninja
meson test --suite setup

and get:
1/3 postgresql:setup / tmp_install               OK 1.56s
2/3 postgresql:setup / install_test_files        OK 0.09s
3/3 postgresql:setup / initdb_cache              FAIL 1.88s   exit status 1

testlog.txt contains:
running bootstrap script ...
----------------------------------- stderr -----------------------------------
TRAP: failed Assert("TYPEALIGN(8, (uintptr_t)(&currval)) == (uintptr_t)(&currval)"), File: 
"...\src\include\port/atomics.h", Line: 597, PID: 7556
child process was terminated by exception 0xC0000409

On f3ff7bf83~1, `meson test --suite setup` passes for me.

(I could not find if support for 32-bit Windows ended, so decided to
report this.)

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Incremental backup from a streaming replication standby
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: cfbot update: Using GitHub for patch review