pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Lakhin <exclusion@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-hackers@lists.postgresql.org, Jaime Casanova <jcasanov@systemguards.com.ec>
Subject: Re: LogwrtResult contended spinlock
Date: Sat, 29 Jun 2024 10:00:00 +0300
Message-ID: <36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com> (raw)
In-Reply-To: <202404071219.p5qphx7vzxte@alvherre.pgsql>
References: <202404071219.p5qphx7vzxte@alvherre.pgsql>

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





view thread (74+ messages)  latest in thread

Message-ID: <36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com>
Permalink:  ../36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com/
Also on:    postgresql.org/message-id/36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: exclusion@gmail.com, alvherre@alvh.no-ip.org, bharath.rupireddyforpostgres@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql@j-davis.com, jcasanov@systemguards.com.ec
  Subject: Re: LogwrtResult contended spinlock
  In-Reply-To: <36796438-a718-cf9b-2071-b2c1b947c1b5@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox