Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Salvatore Dipietro <dipietro(dot)salvatore(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Salvatore Dipietro <dipiets(at)amazon(dot)com>, blakgeof(at)amazon(dot)com
Subject: Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture
Date: 2025-08-15 20:54:29
Message-ID: aJ-ehcxHsOhV5_3b@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 15, 2025 at 03:25:20PM -0500, Nathan Bossart wrote:
> On Fri, Aug 15, 2025 at 04:13:30PM -0400, Andres Freund wrote:
>> IMO, the only way to actually make pg_stat_statements scale is to move to a
>> model much more like our regular stats. I.e. accumulate counters in backend
>> local memory and only occasionally update the shared stats.
>
> Agreed. I remember discussing something similar at pgconf.dev this year.

BTW I'm planning to give this a try...

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-15 22:03:24 Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture
Previous Message Nathan Bossart 2025-08-15 20:25:20 Re: Remove Instruction Synchronization Barrier in spin_delay() for ARM64 architecture