RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Detecting usr/lib/pgsql/pltcl.so with not-hardened warnings '
Hardened: pltcl.so: FAIL: Gaps were detected in the annobin coverage.  Run with -v to list.
' on i686

This bug seems to be already fixed, as a scratch build from the current version was built and no errors were detected.

Scratch build here: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=21859946

new RPMDiff results here: https://rpmdiff.engineering.redhat.com/run/407284/18/

compared to old RPMDiff: https://rpmdiff.engineering.redhat.com/run/388125/7/

Due to this reasons, the bug will be closed as NOTABUG. If you consider this is a bug, feel free to reopen this issue.

So maybe some build problem has been fixed, but isn't the problem already
compiled into the shipped binaries?

Yes, you are right. This is the last version used by customers. It would be rather better to reopen this bug and wait for the next build. If the RPMDiff will be OK, then it will be closed, since it is not so critical to make release dump and a new build for this issue.

Thank you for your advise!

Moving to postgresql component where the problem actually was.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.