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
Postgres v12 produces a flood of errors as follows:
postgres_1 | 2021-06-23 11:31:13.597 UTC [59] ERROR: column c.relhasoids does not exist at character 245
postgres_1 | 2021-06-23 11:31:13.597 UTC [59] STATEMENT: select n.nspname, c.relname, a.attname, a.atttypid, t.typname, a.attnum, a.attlen, a.atttypmod, a.attnotnull, c.relhasrules, c.relkind, c.oid, pg_get_expr(d.adbin, d.adrelid), case t.typtype when 'd' then t.typbasetype else 0 end, t.typtypmod, c.relhasoids from (((pg_catalog.pg_class c inner join pg_catalog.pg_namespace n on n.oid = c.relnamespace and c.oid = 16405) inner join pg_catalog.pg_attribute a on (not a.attisdropped) and a.attnum > 0 and a.attrelid = c.oid) inner join pg_catalog.pg_type t on t.oid = a.atttypid) left outer join pg_attrdef d on a.atthasdef and d.adrelid = a.attrelid and d.adnum = a.attnum order by n.nspname, c.relname, attnum
Workaround: Fallback to v11.
To be investigated. See discussion here including Docker-specific tips.
The text was updated successfully, but these errors were encountered:
Upgrading to PostgreSQL >11 is now required when upgrading SODAR Core and thus SODAR into Django 4.2, see bihealth/sodar-core#880. Hence I looked into this again.
It seems this is actually problem with old clients used. Hence, we need to be certain clients on containers connecting here will be up-to-date. See bihealth/irods-docker#18.
Postgres v12 produces a flood of errors as follows:
Workaround: Fallback to v11.
To be investigated. See discussion here including Docker-specific tips.
The text was updated successfully, but these errors were encountered: