Horton
Menu

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

Yura Sokolov <y.sokolov@postgrespro.ru>

View thread
From: Yura Sokolov <y.sokolov@postgrespro.ru>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>, Nathan Bossart <nathandbossart@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Daniel Gustafsson <daniel@yesql.se>, 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:20:17Z
Lists: pgsql-hackers 
12.03.2026 10:57, Jakub Wartak пишет:
> I propose simply for now that that if there's consensus to drop the 32-bits
> support, then in the release notes of PG19 we could simply add some
> deprecation notice/warning like "PostgreSQL 19 is _probably_ the last release
> to provide support for 32-bits architectures. Please consider planning upgrade
> to 64-bit architecture." (and this costs us nothing, and gives any potential
> user additional year, and project would have even freedom to continue for
> couple releases still with 32-bits until somebody develops proper patch).

imho, it is possible to declare last version with 32bit support as LTS.
i.e. support Pg18 or Pg19 for 10 years instead of 5 years.

I'd vote for Pg18 to be last 32bit aware :)))

-- 
regards
Yura Sokolov aka funny-falcon

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