| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Bastien Roucariès <rouca(at)debian(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Detection of hadware feature => please do not use signal |
| Date: | 2024-10-31 18:25:34 |
| Message-ID: | 1292593.1730399134@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> On 31/10/2024 19:48, Tom Lane wrote:
>> Maybe we could do it one way on linux and the other way everywhere
>> else, but I do not find that attractive; it just makes it harder
>> to get full test coverage.
> Bastien, would you happen to know how other portable libraries that need
> to run on other operating system do this? We added the SIGILL probe back
> in 2018, there might be better options available now.
It occurs to me to wonder whether the existing code works on Windows.
Windows-on-ARM wasn't a thing we thought about in 2018, but it's
a reasonable target now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tyler | 2024-10-31 18:34:38 | Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically. |
| Previous Message | Heikki Linnakangas | 2024-10-31 18:01:41 | Re: Detection of hadware feature => please do not use signal |