Pg_QoS v1.0.0 stable release is out! - AppstoniA via PostgreSQL Announce

public inbox for [email protected]  
help / color / mirror / Atom feed

From: AppstoniA via PostgreSQL Announce <[email protected]>
To: PostgreSQL Announce <[email protected]>
Subject: Pg_QoS v1.0.0 stable release is out!
Date: Tue, 03 Mar 2026 08:01:45 +0000
Message-ID: <[email protected]> (raw)

We are pleased to announce the first stable release of **Pg_QoS**, a PostgreSQL extension that provides Quality of Service (QoS) style resource governance for sessions and queries.

🔹 **Project overview**

Enforce per-role and per-database limits via ALTER ROLE/DATABASE SET qos.*

- Limit CPU usage by binding the backend to N CPU cores (Linux only); planner integration ensures parallel workers stay within that cap
- Track and cap concurrent transactions and statements (SELECT/UPDATE/DELETE/INSERT)
- Limit work_mem per session
- Fast, reliable cache invalidation across sessions (no reconnect) using a shared epoch mechanism

This makes it easier to ensure fair resource allocation
across different workloads running on the same PostgreSQL instance.

🔹 **Requirements**

- PostgreSQL 15 or newer (officially supported)
- Build toolchain and server headers (pg_config must be available)
- Linux for CPU limiting

🔹 **Packages**

Native packages are now available for the following distributions:

  - **Debian 13** (Trixie)
  - **Ubuntu 24.04** (Noble Numbat)
  - **Red Hat Enterprise Linux (RHEL) 10**
  - **AlmaLinux 10**
  - **CentOS Stream 10**

Packages can be found in the repository releases section and cover all PostgreSQL versions supported by Pg_QoS (15 and newer).

🔹 **Repository**

[https://github.com/appstonia/pg_qos](https://github.com/appstonia/pg_qos)

We welcome comments, suggestions, and contributions from the community.

---
Pg_QoS is developed and maintained by the Appstonia team.

We'd love to hear your feedback via Github issues.

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Pg_QoS v1.0.0 stable release is out!
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox