Re: Drop 32-bit support (was "Re: Fix typo 586/686 in atomics/arch-x86.h")

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tomas Vondra <tv(at)fuzzy(dot)cz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Subject: Re: Drop 32-bit support (was "Re: Fix typo 586/686 in atomics/arch-x86.h")
Date: 2026-03-12 15:32:43
Message-ID: tyupvxgrdwe64jboybtydqcnc7hknkcnrbjk7ijbhmzr3eaa5o@dp5eni5e23en
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-03-12 14:54:58 +0100, Jakub Wartak wrote:
> Right, you might be spot-on: I might have overreacted to this. But probably
> the main question is still valid (and now we have thread! :)). Should we
> maintain builds/testing for 32-bit PostgreSQL in 2026 and beyond?
>
> (Everyone else in IT world is getting rid of support for even 686).

I'm confused the 686 is a good bit older than 64 bit support. i686 is from
1995, the first x86-64 chips are from 2003. And you can run 32bit postgres on
a spanking new x86-64 CPU.

So I don't understand how 686 desupport is related to 32bit support.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-03-12 15:35:48 Re: Streamify more code paths
Previous Message Andres Freund 2026-03-12 15:30:25 Re: Drop 32-bit support (was "Re: Fix typo 586/686 in atomics/arch-x86.h")