You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a geldata 6.4 container with a PostGresSQL backend version < 17 the initialization of the backend fails consistently due to (I think) an issue with SQL Introspection. While #7886 seems to indicate that there is version checking to exclude irrelevant columns per version on versions != 17, this does not seem to be the case.
Column dathasloginevt is marked for v17, however when running any version below 17 the backend bootstrap fails because dathasloginevt is not part of the schema yet is included in the query:
When starting a geldata 6.4 container with a PostGresSQL backend version < 17 the initialization of the backend fails consistently due to (I think) an issue with SQL Introspection. While #7886 seems to indicate that there is version checking to exclude irrelevant columns per version on versions != 17, this does not seem to be the case.
Column dathasloginevt is marked for v17, however when running any version below 17 the backend bootstrap fails because dathasloginevt is not part of the schema yet is included in the query:
Steps to Reproduce:
Tested against 15.10, 16.2 & 16.3 AWS RDS aurora-postgresql backends & local docker [email protected]
The text was updated successfully, but these errors were encountered: