Re: AIX support

AIX PG user <postgres-ibm-aix@wwpdl.vnet.ibm.com>

From: AIX PG user <postgres-ibm-aix@wwpdl.vnet.ibm.com>
To: pgsql-hackers@lists.postgresql.org
Cc: AIX PG user <postgres-ibm-aix@wwpdl.vnet.ibm.com>
Date: 2025-11-03T14:46:05Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Restore AIX support.

  2. pg_createsubscriber: Improve error messages.

  3. Use <stdint.h> and <inttypes.h> for c.h integers.

  4. Stabilize jsonb_path_query test case.

  5. Fix C23 compiler warning

  6. pg_stat_statements: Add tests for nested queries with level tracking

  7. Add missing newline at the end of index_including.sql

  8. Remove AIX support

  9. Fix s_lock.h PPC assembly code to be compatible with native AIX assembler.

  10. Use a non-locking initial test in TAS_SPIN on PPC.

  11. Use LWSYNC in place of SYNC/ISYNC in PPC spinlocks, where possible.

  12. Use mutex hint bit in PPC LWARX instructions, where possible.

  13. Adjust TAS assembly as per recent discussions: use "+m"(*lock) everywhere

  14. Apple's assembler likes the inlined TAS syntax too, so no reason to

  15. Tighten up register usage for inline PPC version of tas().

  16. Put the isync where it's supposed to be.

  17. > > I'll re-check that with the ppc architecture guy here.

  18. Fix PPC s_lock operations to work correctly on multi-CPU machines.

  19. I tried to build PostgreSQL with the following step to see backends hung

  20. Complete merge of all old man page information.

  21. s_lock aix patch.

Hi Heikki, 
Thank you for your feedback.

> This looks weird. Sure, "-O2" makes things faster, but we shouldn't 
> force that here. If you want optimizations, you should use pass 
> CFLAGS="-O2" or CFLAGS="-O3" to configure. And why the special mention 
> of MemSet() and MemSetAlign()?

I have removed these.

> I see there's some references to MAKE_EXPORTS in src/backend/Makefile. 
> They seem related to MKLDEXPORT, but we never set MAKE_EXPORTS. Are they 
> still needed?

If MAKE_EXPORTS is not being used by any platforms other than AIX, we can
consider removing it. However, I’m not entirely certain whether it might still
be required elsewhere.  Since these changes appear to be general and not
strictly AIX-specific, would it be fine to submit them as a separate
patch?

Looking forward to your continued support and guidance.

- Sriram.