Upgrade the postgres image used in production to v15

[mayaCostantini]

Problem statement

Related to discussion in #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

• Deploy the postgres v15 in stage environment and run tests to ensure it is working properly
• Verify this upgrade solves the issue of duplicate entries in the database and eventually [Spike] Implement a solution to clean database from bloat data #2189

[mayaCostantini]

/assign @mayaCostantini @harshad16
/priority important-soon
/sig devsecops

[mayaCostantini]

@harshad16 Please feel free to modify or add acceptance criteria to this issue if you think this is necessary

[harshad16]

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

[mayaCostantini]

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).

[harshad16]

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.

[mayaCostantini]

This should normally fixed by #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.

[harshad16]

Related-to: #2745

[harshad16]

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
#2738

Keeping this issue open for the future, to upgrade to PostgreSQL v15.
/unassign
Moving to blocked.