prioritize
get and set the priority of PostgreSQL backends
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
pg_prioritize | 1.0.4 | ADMIN | PostgreSQL | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 5100 | prioritize | No | Yes | No | Yes | No | Yes | - |
| Related | plan_filter pg_kpart pg_readonly qos block_copy_command safeupdate pg_command_fw pg_strict pg_hint_plan |
|---|
no pg 14 on el9
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PGDG | 1.0.4 | 1817161514 | pg_prioritize | - |
| RPM | PGDG | 1.0.4 | 1817161514 | pg_prioritize_$v | - |
| DEB | PGDG | 1.0.4 | 1817161514 | postgresql-$v-prioritize | - |
Install
You can install pg_prioritize directly. First, make sure the PGDG repository is added and enabled:
Install the extension using pig or apt/yum/dnf:
Install
pig
dnf
apt
Create Extension:
Usage
The prioritize extension exposes getpriority() and setpriority() system calls for PostgreSQL backends, allowing you to renice backend processes from SQL.
Get Backend Priority
Any user may query the priority of any backend.
Set Backend Priority
Superusers can set the priority of any backend. Unprivileged users can only adjust backends with the same role.
Note: priority can only be raised (higher numeric value = lower OS priority). Only root can lower the numeric priority value, and PostgreSQL processes should not run as root.
Batch Operations
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)