Skip to content

Update prerequisites to reflect v5.3 changes #7204

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.

Sign up for GitHub

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

Merged
irmabenitezzapata-creator merged 2 commits into from
Jul 31, 2026
Merged

Update prerequisites to reflect v5.3 changes #7204

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
763bb3d
Update prerequisites to reflect v5.3 changes
nick-ivanov-edb Jul 31, 2026
9c5d877
Apply style cleanup to prerequisites.mdx
irmabenitezzapata-creator Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 22 additions & 3 deletions product_docs/docs/efm/5/installing/prerequisites.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,11 +101,11 @@ The database user specified by the `db.user` property in the `efm.properties` fi
`pg_wal_replay_pause()`


If the `reconfigure.num.sync` or `reconfigure.sync.primary` property is set to `true`, then the db.user requires `pg_read_all_stats` privilege and permissions to run `pg_reload_conf()`.
If the `reconfigure.num.sync` or `reconfigure.sync.primary` property is set to `true`, then the `db.user` requires pg_read_all_stats privilege and permissions to run `pg_reload_conf()`.

For detailed information about each of these functions, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/index.html).

If the `update.physical.slots.period` property is used, then the db.user requires the `REPLICATION` privilege. A database superuser can provide the permissions needed:
If the `update.physical.slots.period` property is used, then the db.user requires the REPLICATION privilege. A database superuser can provide the permissions needed:

```sql
ALTER USER <user_name> REPLICATION;
Expand All @@ -117,4 +117,23 @@ The user must also have permissions to read the values of configuration variable
GRANT pg_read_all_settings TO <user_name>;
```

For more information about `pg_read_all_settings`, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/default-roles.html).
For more information about pg_read_all_settings, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/default-roles.html).

If `auto.rewind` is set to `true`, then the `db.user` requires the pg_checkpoint role to be granted, as the Failover Manager agent will issue a `CHECKPOINT` command prior to executing `pg_rewind`.

The required privileges are summarized in this table:

Privilege | Object | Condition
------------|------------------------|----------
EXECUTE | `pg_current_wal_lsn()` | Always required
EXECUTE | `pg_last_wal_replay_lsn()` | Always required
EXECUTE | `pg_wal_replay_resume()` | Always required
EXECUTE | `pg_wal_replay_pause()` | Always required
EXECUTE | `pg_reload_conf()` | When `reconfigure.num.sync` or `reconfigure.sync.primary` is `true`
REPLICATION | | When the `update.physical.slots.period` property is in effect (non-zero value)

Role | Condition
----------------------|----------
pg_read_all_settings | Always required
pg_read_all_stats | When `reconfigure.num.sync` or `reconfigure.sync.primary` is `true`
pg_checkpoint | When `auto.rewind` is set to `true`
Loading