| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, Andres Freund <andres(at)anarazel(dot)de>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Subject: | Re: LLVM 16 (opaque pointers) |
| Date: | 2023-09-21 00:24:05 |
| Message-ID: | 34036e05460e871024873d7542ceff0b2eaac13c.camel@gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Thomas,
On Thu, 2023-09-21 at 08:22 +1200, Thomas Munro wrote:
> So far I've tested LLVM versions 10, 15, 16, 17, 18 (= their main
> branch) against PostgreSQL versions 14, 15, 16. I've attached the
> versions that apply to master and 16, and pushed back-patches to 14
> and 15 to public branches if anyone's interested[1]. Back-patching
> further seems a bit harder. I'm quite willing to do it, but ... do we
> actually need to, ie does anyone really *require* old PostgreSQL
> release branches to work with new LLVM?
RHEL releases new LLVM version along with their new minor releases every
6 month, and we have to build older versions with new LLVM each time.
From RHEL point of view, it would be great if we can back-patch back to
v12 :(
Regards,
--
Devrim Gündüz
Open Source Solution Architect, PostgreSQL Major Contributor
Twitter: @DevrimGunduz , @DevrimGunduzTR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2023-09-21 00:27:38 | Re: Guiding principle for dropping LLVM versions? |
| Previous Message | Peter Smith | 2023-09-21 00:06:03 | Re: Add 'worker_type' to pg_stat_subscription |