This update for postgresql16 fixes the following issues:
{
"binaries": [
{
"postgresql14": "14.13-150600.16.6.1",
"postgresql14-llvmjit-devel": "14.13-150600.16.6.1",
"postgresql14-plperl": "14.13-150600.16.6.1",
"postgresql14-server-devel": "14.13-150600.16.6.1",
"postgresql14-contrib": "14.13-150600.16.6.1",
"postgresql14-docs": "14.13-150600.16.6.1",
"postgresql14-plpython": "14.13-150600.16.6.1",
"postgresql14-test": "14.13-150600.16.6.1",
"postgresql14-pltcl": "14.13-150600.16.6.1",
"postgresql14-llvmjit": "14.13-150600.16.6.1",
"postgresql14-devel": "14.13-150600.16.6.1",
"postgresql14-server": "14.13-150600.16.6.1"
}
]
}{
"binaries": [
{
"postgresql14": "14.13-150600.16.6.1",
"postgresql14-server-devel": "14.13-150600.16.6.1",
"postgresql14-plperl": "14.13-150600.16.6.1",
"postgresql14-contrib": "14.13-150600.16.6.1",
"postgresql14-docs": "14.13-150600.16.6.1",
"postgresql14-plpython": "14.13-150600.16.6.1",
"postgresql14-pltcl": "14.13-150600.16.6.1",
"postgresql14-devel": "14.13-150600.16.6.1",
"postgresql14-server": "14.13-150600.16.6.1"
}
]
}