This update for postgresql16 fixes the following issues:
Upgrade to 16.8:
{ "binaries": [ { "postgresql16-plperl": "16.8-150600.16.15.1", "postgresql16-server-devel": "16.8-150600.16.15.1", "postgresql16-docs": "16.8-150600.16.15.1", "postgresql16-devel": "16.8-150600.16.15.1", "postgresql16-server": "16.8-150600.16.15.1", "postgresql16-plpython": "16.8-150600.16.15.1", "postgresql16-contrib": "16.8-150600.16.15.1", "postgresql16-pltcl": "16.8-150600.16.15.1" } ] }
{ "binaries": [ { "postgresql16-plperl": "16.8-150600.16.15.1", "postgresql16-llvmjit-devel": "16.8-150600.16.15.1", "postgresql16-docs": "16.8-150600.16.15.1", "postgresql16-llvmjit": "16.8-150600.16.15.1", "postgresql16-devel": "16.8-150600.16.15.1", "postgresql16-server": "16.8-150600.16.15.1", "postgresql16-plpython": "16.8-150600.16.15.1", "postgresql16-test": "16.8-150600.16.15.1", "postgresql16-server-devel": "16.8-150600.16.15.1", "postgresql16-contrib": "16.8-150600.16.15.1", "postgresql16-pltcl": "16.8-150600.16.15.1", "postgresql16": "16.8-150600.16.15.1" } ] }