Add macro documentation comments to AC_DEFINE for FTS and OpenSSL option

[yjhjstz]

Fixes #1058

What does this PR do?

Type of Change

• Bug fix (non-breaking change)
• New feature (non-breaking change)
• Breaking change (fix or feature with breaking changes)
• Documentation update

Breaking Changes

Test Plan

• Unit tests added/updated
• Integration tests added/updated
• Passed make installcheck
• Passed make -C src/test installcheck-cbdb-parallel

Impact

Performance:

User-facing changes:

Dependencies:

Checklist

• Followed contribution guide
• Added/updated documentation
• Reviewed code for security implications
• Requested review from cloudberry committers

Additional Context

CI Skip Instructions

---

[tuhaihe]

Hey @yjhjstz thanks!

During my test, after running autoreconf -i, the file pg_config.h.in also had some related updates:

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   src/include/pg_config.h.in

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	src/include/pg_config.h.in~

Could you help take a look again? Thanks!

[yjhjstz]

Hey @yjhjstz thanks!

During my test, after running autoreconf -i, the file pg_config.h.in also had some related updates:

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   src/include/pg_config.h.in

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	src/include/pg_config.h.in~

Could you help take a look again? Thanks!

pg_config.h.in is automatically generated by autoheader, which dynamically creates comment templates based on the macro definitions (e.g., AC_DEFINE, AC_CHECK_FUNCS) in your configure.ac file.

added src/include/pg_config.h.in.

[tuhaihe]

Could you help take a look again? Thanks!

pg_config.h.in is automatically generated by autoheader, which dynamically creates comment templates based on the macro definitions (e.g., AC_DEFINE, AC_CHECK_FUNCS) in your configure.ac file.

added src/include/pg_config.h.in.

Thanks. One more point is that after pulling your branch, I ran the command autoreconf -i again, the file configure had some changes, is there a need to commit its changes again?

Other than this, all looks good to me. Thanks!

[yjhjstz]

Could you help take a look again? Thanks!

pg_config.h.in is automatically generated by autoheader, which dynamically creates comment templates based on the macro definitions (e.g., AC_DEFINE, AC_CHECK_FUNCS) in your configure.ac file.
added src/include/pg_config.h.in.

Thanks. One more point is that after pulling your branch, I ran the command autoreconf -i again, the file configure had some changes, is there a need to commit its changes again?

Other than this, all looks good to me. Thanks!

I think no need.

[tuhaihe]

Maybe need to rerun the cmd autoreconf -i to generate the new file.

Without any change, after running the cmd, some files changed:

	modified:   configure
	modified:   src/include/pg_config.h.in

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	src/include/pg_config.h.in~

[yjhjstz]

Maybe need to rerun the cmd autoreconf -i to generate the new file.

Without any change, after running the cmd, some files changed:

	modified:   configure
	modified:   src/include/pg_config.h.in

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	src/include/pg_config.h.in~

Maybe need to rerun the cmd autoreconf -i to generate the new file.

Without any change, after running the cmd, some files changed:

	modified:   configure
	modified:   src/include/pg_config.h.in

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	src/include/pg_config.h.in~

updated.