This update for postgresql16 fixes the following issues:
Upgraded to 16.11:
Other fixes:
{
"binaries": [
{
"postgresql16-pltcl": "16.11-150600.16.25.1",
"postgresql16-devel": "16.11-150600.16.25.1",
"postgresql16-test": "16.11-150600.16.25.1",
"postgresql16-server": "16.11-150600.16.25.1",
"postgresql16-docs": "16.11-150600.16.25.1",
"postgresql16-plpython": "16.11-150600.16.25.1",
"postgresql16-contrib": "16.11-150600.16.25.1",
"postgresql16-plperl": "16.11-150600.16.25.1",
"postgresql16-llvmjit": "16.11-150600.16.25.1",
"postgresql16": "16.11-150600.16.25.1",
"postgresql16-llvmjit-devel": "16.11-150600.16.25.1",
"postgresql16-server-devel": "16.11-150600.16.25.1"
}
]
}{
"binaries": [
{
"postgresql16-pltcl": "16.11-150600.16.25.1",
"postgresql16-devel": "16.11-150600.16.25.1",
"postgresql16-server": "16.11-150600.16.25.1",
"postgresql16-docs": "16.11-150600.16.25.1",
"postgresql16-plpython": "16.11-150600.16.25.1",
"postgresql16-contrib": "16.11-150600.16.25.1",
"postgresql16-plperl": "16.11-150600.16.25.1",
"postgresql16-server-devel": "16.11-150600.16.25.1"
}
]
}