From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Krunal Bauskar <krunalbauskar(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Improving spin-lock implementation on ARM. |
Date: | 2020-11-30 21:01:41 |
Message-ID: | CAPpHfdttqGxB4khzZWEZic1EFyBcqRhDOD2Fmp3z+Vmfyqd0hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 30, 2020 at 7:00 AM Krunal Bauskar <krunalbauskar(at)gmail(dot)com> wrote:
> 3. Problem with GCC approach is still a lot of distro don't support gcc 9.4 as default.
> To use this approach:
> * PGSQL will have to roll out its packages using gcc-9.4+ only so that they are compatible with all aarch64 machines
> * but this continues to affect all other users who tend to build pgsql using standard distro based compiler. (unless they upgrade compiler).
I think if a user, who runs PostgreSQL on a multicore machine with
high-concurrent load, can take care about installing the appropriate
package/using the appropriate compiler (especially if we publish
explicit instructions for that). In the same way such advanced users
tune Linux kernel etc.
BTW, how do you get that required gcc version is 9.4? I've managed to
use LSE with gcc 9.3.
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2020-11-30 21:03:26 | Re: Printing LSN made easy |
Previous Message | Alexander Korotkov | 2020-11-30 20:46:44 | Re: Improving spin-lock implementation on ARM. |