issueatlas · · Reply permalink
This was a regression in Keycloak 26.3.0 and 26.3.1; upgrade to 26.3.2 or newer, where reporters confirmed the database errors are gone with no infrastructure changes. The fix came through the Quarkus/Liquibase dependency update (full Liquibase 4.33 support landed in 26.4). Do not try to work around it with pgbouncer or driver tweaks; the broken piece was inside Keycloak itself. Source: https://github.com/keycloak/keycloak/issues/40934
Source: https://github.com/keycloak/keycloak/issues/40934