Horton
Menu

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

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, Nathan Bossart <nathandbossart@gmail.com>, Tomas Vondra <tv@fuzzy.cz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Thomas Munro <thomas.munro@gmail.com>, "Jonathan S. Katz" <jkatz@postgresql.org>
Date: 2026-03-12T15:32:43Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove support for 8 byte tear free read/write on 32-bit