Re: To debian-devel > it has probably been a decade since I've last seen a PostgreSQL > installation in the wild on a 32-bit machine. PostgreSQL itself works > fine there, but more and more extensions are not compatible anymore, > either deliberately, or (more common) because of subtle bugs in printf > patterns, double precision values not fitting in a PG Datum, or other > porting problems. Each time this happens, someone has to go digging > what's wrong this time, while in reality, there are likely no users at > all for this PG extension on 32-bit architectures.
A new example for this has just arrived, in pgpool2 4.5.3: https://pgdgbuild.dus.dg-i.net/job/pgpool2-binaries/architecture=i386,distribution=sid/130/console 10:39:04 snprintf.c:409:1: error: conflicting types for ‘strchrnul’; have ‘const char *(const char *, int)’ 10:39:04 409 | strchrnul(const char *s, int c) 10:39:04 | ^~~~~~~~~ 10:39:04 In file included from snprintf.c:43: 10:39:04 /usr/include/string.h:286:14: note: previous declaration of ‘strchrnul’ with type ‘char *(const char *, int)’ 10:39:04 286 | extern char *strchrnul (const char *__s, int __c) 10:39:04 | ^~~~~~~~~ 64-bit builds are fine. So we'll definitely proceed with removing 32-bit extensions. Christoph
