Editing GitLab V18 Upgrade (section)

==Method 2: Persistent Grant (via Helm `values.yaml`)==

This is the preferred method for Helm deployments as it ensures the grant is applied consistently.

You can inject an initialization script into the PostgreSQL container that grants the necessary permissions. This typically involves using the `postgresql.initdb` configuration in your `values.yaml`.

===Example `values.yaml` addition:===


 # Add this to your values.yaml file
 postgresql:
   # This section assumes you are using the bundled PostgreSQL with the GitLab chart.
   # If using an external PostgreSQL, you would need to run this command on your external DB.
   initdb:
     ## @param initdb.scripts Allows mounting scripts into /docker-entrypoint-initdb.d/ to be executed at first boot of the Postgres container
     ## This can be used for custom grants or other database initialization.
     scripts:
       grant-wal-permissions.sql: |
         DO
         $do$
         BEGIN
           IF EXISTS (SELECT 1 FROM pg_catalog.pg_proc p JOIN pg_catalog.pg_namespace n ON p.pronamespace = n.oid WHERE p.proname = 'pg_ls_waldir' AND n.nspname = 'pg_catalog') THEN
             GRANT EXECUTE ON FUNCTION pg_catalog.pg_ls_waldir() TO gitlab; -- Replace 'gitlab' with your actual GitLab database user if different
           END IF;
           -- Also consider granting pg_monitor role if appropriate for your security model
           IF EXISTS (SELECT 1 FROM pg_roles WHERE rolname = 'pg_monitor') THEN
             GRANT pg_monitor TO gitlab; -- Replace 'gitlab' with your actual GitLab database user if different
           END IF;
         END
         $do$;


===Explanation of the `initdb.scripts` addition:===

* `initdb.scripts`: This section allows you to define custom SQL scripts that will be run when the PostgreSQL container is first initialized.
* `grant-wal-permissions.sql`: This is a descriptive name for your script.
* `DO $$BEGIN ... END$$;`: This is an anonymous PL/pgSQL block, which allows for conditional logic (like checking if the function exists before trying to grant).
* `IF EXISTS (...) THEN ... END IF;`: This checks if `pg_ls_waldir` function exists (useful for PostgreSQL version compatibility) and if the `pg_monitor` role exists before attempting the `GRANT`.
* `TO gitlab;`: **Crucially, replace `gitlab` with the actual database user GitLab uses.** This is usually configured in your GitLab Helm chart's `global.psql.username` or `global.postgresql.username` setting, or if you're using the bundled PostgreSQL, it's often `gitlab`.

===After modifying `values.yaml`:===

Run the `helm upgrade` command again:

 helm upgrade <your-gitlab-release-name> gitlab/gitlab -f your_values.yaml --version <new-gitlab-version>