This update for postgresql17 fixes the following issues:
Upgrade to 17.4:
{ "binaries": [ { "libecpg6": "17.4-150600.13.10.1", "postgresql17-devel": "17.4-150600.13.10.1", "postgresql17-plpython": "17.4-150600.13.10.1", "postgresql17-contrib": "17.4-150600.13.10.1", "postgresql17-server-devel": "17.4-150600.13.10.1", "postgresql17-plperl": "17.4-150600.13.10.1", "postgresql17-pltcl": "17.4-150600.13.10.1", "postgresql17-docs": "17.4-150600.13.10.1", "postgresql17-server": "17.4-150600.13.10.1" } ] }
{ "binaries": [ { "libecpg6": "17.4-150600.13.10.1", "libpq5-32bit": "17.4-150600.13.10.1", "postgresql17": "17.4-150600.13.10.1", "postgresql17-llvmjit": "17.4-150600.13.10.1", "postgresql17-plperl": "17.4-150600.13.10.1", "postgresql17-test": "17.4-150600.13.10.1", "libpq5": "17.4-150600.13.10.1", "postgresql17-devel": "17.4-150600.13.10.1", "postgresql17-plpython": "17.4-150600.13.10.1", "libecpg6-32bit": "17.4-150600.13.10.1", "postgresql17-contrib": "17.4-150600.13.10.1", "postgresql17-llvmjit-devel": "17.4-150600.13.10.1", "postgresql17-server-devel": "17.4-150600.13.10.1", "postgresql17-pltcl": "17.4-150600.13.10.1", "postgresql17-docs": "17.4-150600.13.10.1", "postgresql17-server": "17.4-150600.13.10.1" } ] }