Skip to content

Releases: ozontech/pg_doorman

2.2.2 (Aug 17, 2025)

17 Aug 15:50
b93b40c

Choose a tag to compare

Features:

  • Added new generate feature functionality

Bug Fixes:

  • Fixed deallocate issues with PGX5 compatibility

2.2.1 (Aug 6, 2025)

06 Aug 07:48
5713e33

Choose a tag to compare

Features:

  • Improve Prometheus exporter functionality

2.2.0 (Aug 5, 2025)

05 Aug 20:13
5c14ab0

Choose a tag to compare

2.2.0 (Aug 5, 2025) Pre-release
Pre-release

Features:

  • Added Prometheus exporter functionality that provides metrics about connections, memory usage, pools, queries, and transactions

2.1.2 (Aug 4, 2025)

04 Aug 19:36
76e4347

Choose a tag to compare

Features:

  • Added docker image ghcr.io/ozontech/pg_doorman

2.1.1 (Aug 4, 2025)

04 Aug 18:40
c6ce0f6

Choose a tag to compare

2.1.1 (Aug 4, 2025) Pre-release
Pre-release

Features:

  • public docker images

2.1.0 (Aug 1, 2025)

01 Aug 15:20
3c860a4

Choose a tag to compare

Features:

  • The new command generate connects to your PostgreSQL server, automatically detects all databases and users, and creates a complete configuration file with appropriate settings. This is especially useful for quickly setting up PgDoorman in new environments or when you have many databases and users to configure.

2.0.1 (Jul 24, 2025)

24 Jul 19:29
25337a4

Choose a tag to compare

  • Fix "memory-leak" while processing client messages.

2.0.0 (Jul 22, 2025)

22 Jul 15:09

Choose a tag to compare

  • Added tls_mode configuration option to enhance security with flexible TLS connection management and client certificate validation capabilities.

1.9.0 (Jul 20, 2025)

20 Jul 17:30
691cf6f

Choose a tag to compare

  • Added pam auth support.
  • Added talos (yet another jwt auth support).
  • When using the COPY protocol, if a row contains a large column, pg_doorman may run out of memory. Now this happens when streaming, when the response is not stored in memory.
  • Updating rust and tokio.

v1.8.3

11 Jun 06:08
34082ec

Choose a tag to compare

1.8.3 (Jun 11, 2025)

Fixed

  • Critical bug: if a free connection was not available on the Server in pool (query_wait_timeout), the Client's buffer was not cleared, leading to an incorrect response error #38.
  • Ngsql issue: npgsql/npgsql#6115.