Re: Detection of hadware feature => please do not use signal

From: Bastien Roucariès <rouca(at)debian(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Detection of hadware feature => please do not use signal
Date: 2024-11-01 10:20:03
Message-ID: 7915750.ZPPAYPQ7GT@portable-bastien
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Le vendredi 1 novembre 2024, 06:16:32 UTC Tom Lane a écrit :
> I wrote:
> > Hmm. So it seems like we could do this:
> > * Linux, FreeBSD, OpenBSD: do run-time test as recommended
> > * Windows, macOS: assume that supported ARM hardware can do this
> > * anything else: assume no hardware CRC
>
> Actually, after chewing on that second point awhile longer,
> how about this modest proposal:
>
> * Drop all code for run-time determination of ARM CRC support.
> Assume it's there unless user builds with a -march option that
> says it definitely isn't.
>
> Realistically, exactly who is going to be running Postgres 18+
> on ARM hardware that lacks CRC support? I can think of lots of
> projects that are more worthy of our time than this.
>
> (Perhaps it's time to apply the same mindset to x86 CRC support
> too?)

arm64 baseline for debian is without CRC so I will prefer to keep crc32

Bastien
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-11-01 17:12:03 Re: BUG #18682: Null grouping set with empty table returns a row contains null.
Previous Message David Rowley 2024-11-01 09:03:08 Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically.