Re: LogwrtResult contended spinlock

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Subject: Re: LogwrtResult contended spinlock
Date: 2024-07-02 05:00:00
Message-ID: 72705e42-42d1-ac6e-e7d5-4baec8a0d2af@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

01.07.2024 20:04, Alvaro Herrera wrote:
> OK, so it's
> #if ALIGNOF_LONG_LONG_INT >= 8
>
> Alexander, can you please confirm whether this works for you?

Yes, the v4 patch makes `meson test --suite setup` pass in x86 environment.
And complete `meson test` fails on pg_amcheck/004_verify_heapam only
(I think it's a separate issue, just want to announce what else is broken
on that platform)

Thank you!

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-07-02 05:29:20 Re: Pgoutput not capturing the generated columns
Previous Message David Rowley 2024-07-02 04:49:52 Re: Speed up JSON escape processing with SIMD plus other optimisations