This update for postgresql18 fixes the following issues:
{
"binaries": [
{
"libecpg6": "18.3-160000.1.1",
"libpq5": "18.3-160000.1.1",
"postgresql18": "18.3-160000.1.1",
"postgresql18-contrib": "18.3-160000.1.1",
"postgresql18-devel": "18.3-160000.1.1",
"postgresql18-devel-mini": "18.3-160000.1.1",
"postgresql18-docs": "18.3-160000.1.1",
"postgresql18-llvmjit": "18.3-160000.1.1",
"postgresql18-llvmjit-devel": "18.3-160000.1.1",
"postgresql18-plperl": "18.3-160000.1.1",
"postgresql18-plpython": "18.3-160000.1.1",
"postgresql18-pltcl": "18.3-160000.1.1",
"postgresql18-server": "18.3-160000.1.1",
"postgresql18-server-devel": "18.3-160000.1.1",
"postgresql18-test": "18.3-160000.1.1"
}
]
}
{
"binaries": [
{
"libecpg6": "18.3-160000.1.1",
"libpq5": "18.3-160000.1.1",
"postgresql18": "18.3-160000.1.1",
"postgresql18-contrib": "18.3-160000.1.1",
"postgresql18-devel": "18.3-160000.1.1",
"postgresql18-devel-mini": "18.3-160000.1.1",
"postgresql18-docs": "18.3-160000.1.1",
"postgresql18-llvmjit": "18.3-160000.1.1",
"postgresql18-llvmjit-devel": "18.3-160000.1.1",
"postgresql18-plperl": "18.3-160000.1.1",
"postgresql18-plpython": "18.3-160000.1.1",
"postgresql18-pltcl": "18.3-160000.1.1",
"postgresql18-server": "18.3-160000.1.1",
"postgresql18-server-devel": "18.3-160000.1.1",
"postgresql18-test": "18.3-160000.1.1"
}
]
}