Date: Sun, 28 Jul 2024 19:44:26 +0300
From: Christoph Berg <myon@debian.org>
To: Bradford Boyle <bradford.d.boyle@gmail.com>
Cc: pgsql-pkg-debian@lists.postgresql.org, andrew@ankane.org
Subject: The end of 32-bit PostgreSQL support?
Message-ID: <ZqZ1agsCfHd9eRU0@msg.df7cb.de>
References: 
 <CAOMoQbQak2uyt5oGUaTWHPn3nWo+Q97JWGMWM-bqq6yFWFw+gw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAOMoQbQak2uyt5oGUaTWHPn3nWo+Q97JWGMWM-bqq6yFWFw+gw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZqZ1agsCfHd9eRU0%40msg.df7cb.de>
Precedence: bulk

Re: Bradford Boyle
> pgvector has released 0.7.3 and I have update the packaging on Salsa [1] to
> update the Debian package. I'd like to request a review and upload, as
> cycles permit.

Hi Bradford,

thanks, uploaded!

> There was a build failure for sid/i386 in Salsa's CI pipeline. I suspect
> this was caused by the new addition of gcc-14 to sid since the
> problematic code was unchanged between 0.7.2 and 0.7.3. Reviewing the
> console output from Salsa's pipeline for 0.7.2 [2], shows that gcc-13
> was used for building 0.7.2. I was able to resolve the build failure by
> conditionally adding -msse2 to PG_CFLAGS when DEB_HOST_ARCH is i386.

Having seen how much time you had to spend on resolving this, I wonder
it it is finally time to sunset the support for 32-bit architectures
in PostgreSQL on Debian. I can't even remember when I've seen a 32-bit
cluster in the wild, and there's been zero complaints when I disabled
i386 support on apt.postgresql.org for bullseye. There is a steady
stream of extension bugs specific to 32-bit, upstreams have little way
and incentive to fix that, and we waste a lot of time for probably no
users.

Comments? Disable it all (but keep libpq5 for applications)? Continue
to build the server since it works, but disable building all
extensions?

Christoph