This update for postgresql16 fixes the following issues:
Upgrade to 16.2:
{
"binaries": [
{
"postgresql16": "16.2-3.10.1",
"libecpg6-32bit": "16.2-3.10.1",
"postgresql16-docs": "16.2-3.10.1",
"postgresql16-plperl": "16.2-3.10.1",
"postgresql16-contrib": "16.2-3.10.1",
"postgresql16-pltcl": "16.2-3.10.1",
"postgresql16-server": "16.2-3.10.1",
"libpq5": "16.2-3.10.1",
"libecpg6": "16.2-3.10.1",
"postgresql16-plpython": "16.2-3.10.1",
"libpq5-32bit": "16.2-3.10.1"
}
]
}{
"binaries": [
{
"postgresql16": "16.2-3.10.1",
"libecpg6-32bit": "16.2-3.10.1",
"postgresql16-docs": "16.2-3.10.1",
"postgresql16-plperl": "16.2-3.10.1",
"postgresql16-contrib": "16.2-3.10.1",
"postgresql16-pltcl": "16.2-3.10.1",
"postgresql16-server": "16.2-3.10.1",
"libpq5": "16.2-3.10.1",
"libecpg6": "16.2-3.10.1",
"postgresql16-plpython": "16.2-3.10.1",
"libpq5-32bit": "16.2-3.10.1"
}
]
}