Hi Tom,
Yes, there is something strange with _LARGE_FILES in 32bit.
However, that exists too with version 10.4 and 9.6.9 , and tests are 100% OK.
So, it seems that something new appears within v11
v11beta1 brings new json files. Either these files reveal some issue on AIX
32bit or they contain code that is not compatible with AIX environment and some
change should be applied...
Cordialement,
Tony Reix
ATOS / Bull SAS
ATOS Expert
IBM Coop Architect & Technical Leader
Office : +33 (0) 4 76 29 72 67
1 rue de Provence - 38432 Échirolles - France
www.atos.net
________________________________________
De : Tom Lane [t...@sss.pgh.pa.us]
Envoyé : jeudi 31 mai 2018 16:28
À : REIX, Tony
Cc : Alvaro Herrera; PostgreSQL-development; APEKE, SENA (ext); Peter
Eisentraut; Anthony Bykov; Noah Misch
Objet : Re: PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode
"REIX, Tony" <tony.r...@atos.net> writes:
> It looks like configure does figure out that LARGE_FILES is required, only in
> 32bit.
> No need in 64bit.
Check ...
> However, in 32bit, though there is:
> #define _LARGE_FILES 1
> in file :
> src/include/pg_config.h
> I had to add it at the beg of file by means of a patch to several files:
This is surely not what's intended. It seems like plpython is messing
things up somehow, probably through an #include-ordering error, but
I don't see the exact problem offhand.
I wondered why the existing 32-bit AIX buildfarm machines aren't showing
problems, but looking closer at them, they are manually forcing
_LARGE_FILES, which probably is masking things:
'config_env' => {
'CC' => 'wrap-gcc -D_THREAD_SAFE=1 -D_LARGE_FILES=1
-maix32',
Noah, why'd you do that, and would you be willing to remove it? IMO
Postgres should work without that.
regards, tom lane
