Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL >11 produces errors #1

Closed
mikkonie opened this issue Jun 23, 2021 · 2 comments
Closed

PostgreSQL >11 produces errors #1

mikkonie opened this issue Jun 23, 2021 · 2 comments
Assignees
Labels
bug Bug to be fixed

Comments

@mikkonie
Copy link
Contributor

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.

@mikkonie mikkonie added the bug Bug to be fixed label Jun 24, 2021
@mikkonie mikkonie changed the title PostgreSQL v12 produces errors PostgreSQL >11 produces errors Jan 9, 2024
@mikkonie
Copy link
Contributor Author

mikkonie commented Jan 9, 2024

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.

@mikkonie mikkonie self-assigned this Jan 9, 2024
@mikkonie
Copy link
Contributor Author

Closing this issue as it will be handled within the irods-docker repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug to be fixed
Projects
None yet
Development

No branches or pull requests

1 participant