> What you do need to do to reproduce the described problems is
> check out the Postgres git tree and rewind to just before
> commit 0b16bb877, where we deleted AIX support.  Any attempt
> to restore AIX support would have to start with reverting that
> commit (and perhaps the followup f0827b443).

>                         regards, tom lane

Hi Team, thank you for all the info.

We progressed to build the source on our nodes and the build was successful with the below configuration.

Postgres              - github-bcdfa5f2e2f

AIX                         - 71c

Xlc                         - 13.1.0

Bison                    - 3.0.5

Going ahead, we want to build the changes that were removed as part of “0b16bb8776bb8”, with latest Xlc and gcc version.

We were building the source from the postgres ftp server(https://ftp.postgresql.org/pub/source/), would like to understand if there are any source level changes between the ftp server and the source on github?

Regards,

Sriram.

From: Tom Lane <[email protected]>
Date: Friday, 29 March 2024 at 9:03 AM
To: Thomas Munro <[email protected]>
Cc: Noah Misch <[email protected]>, Sriram RK <[email protected]>, Alvaro Herrera <[email protected]>, [email protected] <[email protected]>
Subject: Re: AIX support

Thomas Munro <[email protected]> writes:
> Oh, sorry, I had missed the part where newer compilers fix the issue
> too.  Old out-of-support versions of AIX running old compilers, what
> fun.

Indeed.  One of the topics that needs investigation if you want to
pursue this is which AIX system and compiler versions still deserve
support, and which of the AIX hacks we had been carrying still need
to be there based on that analysis.  For context, we've been pruning
support for extinct-in-the-wild OS versions pretty aggressively
over the past couple of years, and I'd expect to apply the same
standard to AIX.

                        regards, tom lane