Should we call it quits on support for 32-bit

Paul Ramsey pramsey at cleverelephant.ca
Mon Aug 19 15:37:24 PDT 2024


I feel fine about it, since I have been unable to get access to sufficiently working 32 bit development environments to attack the problem, despite quite a number of tries, and zero issues from any of our customers. Even the loons still running RHEL7 apparently aren’t lunatic enough to be doing it on a 32-bit machine.

Would I like to be able debug those issues? I would theoretically, but the practical requirement to invest multiple days to (slowly slowly slowly) get a dev env working means I just never actually *do*, since there’s no reward for doing so, save in heaven after I pass.

P

> On Aug 19, 2024, at 3:33 PM, Regina Obe <lr at pcorp.us> wrote:
> 
> I feel a little uneasy about declaring 32-bit systems dead, but
> apt.postgresql.org (and I assume Debian upstream), is about to declare no
> longer supporting 32-bit systems.
> 
> How do people feel about this.  On the one hand I feel like some of those
> 32-bit failures deserve further investigation.
> 
> Poor berrie has been crashing on garden tests ST_MakePolygon(Nan ...) for a
> while, I'm sure it's fixable, and it's our fault and we should do something
> about it, but berrie64 is doing fine on the same tests.
> 
> And this - https://trac.osgeo.org/postgis/ticket/5461  
> 
> And I can't remember the last time I saw 32-bit gitlab happy -
> https://gitlab.com/postgis/postgis/-/jobs/7550985291
> 
> Part of me worries, are these true errors we are only seeing because of the
> smaller bit space or have we just gone beyond 32-bit that we just shouldn't
> care.
> 
> Anyone have thoughts on the matter?
> 
> Thanks,
> Regina
> 
> 
> 
> 



More information about the postgis-devel mailing list