Open mayaCostantini opened 2 years ago
/assign @mayaCostantini @harshad16 /priority important-soon /sig devsecops
@harshad16 Please feel free to modify or add acceptance criteria to this issue if you think this is necessary
Currently we are using rhscl/postgresql-10-rhel7 Redhat currently offers following images: https://catalog.redhat.com/software/containers/search?q=postgresql&p=1&vendor_name=Red%20Hat
I see the postgres 15 image is not available yet on the Red Hat catalog. Do you think we could wait for it to be released and experiment with a community image in test environment in the meantime? I am not sure if using a community image would change anything (from an operational point of view).
We should explore the way in source code to fix this issue of Null being treated as unquie , if possible Using the community image should be an option is nothing else is working.
This should normally fixed by https://github.com/thoth-station/storages/pull/2738, but I think changing the image would still be a good idea in the long term. Let's downgrade the priority of this issue in the meantime.
We would have to wait for redhat support PostgreSQL-15 to be available. https://catalog.redhat.com/software/containers/search?q=postgresql&p=1&vendor_name=Red%20Hat
Till then we have fix for null value being treated as distinct https://github.com/thoth-station/storages/pull/2738
Keeping this issue open for the future, to upgrade to PostgreSQL v15. /unassign Moving to blocked.
Problem statement
Related to discussion in https://github.com/thoth-station/storages/issues/2729 We need to upgrade the postgres image used in prod to v15 to solve the unique constraint violation issue described in the issue above.
Proposal description