CHANGE DESCRIPTION

Problem:
The logs show the following error message: "stderr": "psql::5: ERROR: role "username" does not exist
This occurred in this part of the method:
GRANT ALL PRIVILEGES ON SCHEMA public TO :"username";
The problem is with using :"username" in the SQL. This kind of placeholder works for values, but not for names like roles, or users.
Names (called identifiers) must be written directly in the SQL. Placeholders don’t work for them.
In our case:
GRANT ALL PRIVILEGES ON SCHEMA public TO :"username";
PostgreSQL looks for a role literally named "username", instead of using the actual value. Since that role doesn’t exist, we get an error.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Instead of using a placeholder like :"username" in the SQL, we insert the actual username directly into the SQL string.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?