# Release Notes

## :label: v3.9.2

*<mark style="color:blue;">May 21, 2026</mark>*

### Fixes

> * **Empty tag handling**\
>   The agent now automatically strips empty tags before transmission. Previously, an empty tag could occasionally be sent to the platform, causing an insertion error in the metrics database.
> * **Application name sanitization**\
>   The `application_name` value retrieved from [`pg_stat_activity`](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW) is automatically added as a tag, but could sometimes contain special formats, that triggered an insertion error in the metrics database. The agent now strips any content enclosed in parentheses before transmitting the tag.

## :label: v3.9.0

*<mark style="color:blue;">Feb 02, 2026</mark>*

### Changes

> * Allows switching from an MD5-based query identifier to PostgreSQL’s native `queryid`.\
>   [Refer to the documentation](/manual/features/tips-and-hints/query-identifier.md) for more details.
> * Added the `DATASENTINEL_FOREGROUND` environment variable to facilitate [automatic startup via a systemd service](/manual/implementation/troubleshooting/unexpected-agent-termination.md).

## :label: v3.8.0

*<mark style="color:blue;">Nov 12, 2025</mark>*

### Changes

> * Fully compatible with the newest release, [PostgreSQL Version 18.](https://www.postgresql.org/docs/18/index.html)
> * Updated third-party libraries.

### Fixes

> **Solaris Compatibility for `system_stats` Extension:**\
> Resolved an issue where the current [system\_stats](https://github.com/EnterpriseDB/system_stats) extension running on Solaris systems was missing certain metric fields.

## :label: v3.7.0

*<mark style="color:blue;">Jun 9, 2025</mark>*

### Changes

> The agent now includes the **PostgreSQL listening port** in the metadata it sends to the repository. This enables the repository to track database connection endpoints.

### Fixes

> * **Extension Compatibility Update:**\
>   The agent now detects the version of the [pg\_store\_plans extension](/manual/getting-started/postgresql-clusters/extensions/pg_store_plans.md) and adjusts its queries accordingly. It automatically runs the appropriate query to collect metrics based on the detected version.\
>   This ensures compatibility with [version 1.9](https://github.com/ossc-db/pg_store_plans) (related to [PostgreSQL 17](https://www.postgresql.org/docs/17/index.html)), which includes renamed columns.

## :label: v3.6.0

*<mark style="color:blue;">Oct 15, 2024</mark>*

### Changes

> * Fully compatible with the newest release, [PostgreSQL Version 17.](https://www.postgresql.org/docs/17/index.html)
> * Replaced WSGI CherryPy, a web framework, with Uvicorn, an ASGI web server optimized for handling asynchronous requests.\
>   The agent now includes a **hard-coded limit** for the maximum size of the `api_calls.log` file. The log file **cannot exceed 10MB**, ensuring better management of disk usage and avoiding unbounded growth
> * Updated third-party libraries.
> * Internal memory management improvements

## :label: v3.5.2

*<mark style="color:blue;">Apr 10, 2024</mark>*

### Changes

> * Fully compatible with the newest release, [PostgreSQL Version 16.](https://www.postgresql.org/docs/16/index.html)
> * Updated third-party libraries.
> * Send any issues encountered during instance monitoring directly to the platform.

#### Fixes

> Error occurred with **archive\_mode** set to **always.**

## :label: v3.5.1

*<mark style="color:blue;">Mar 20, 2024</mark>*

#### Fixes

> Every query text is now automatically converted to UTF-8 format before sending to our platform, sidestepping issues with non-ASCII characters like accents

## :label: v3.5.0

*<mark style="color:blue;">Jan 22, 2024</mark>*

#### Changes

> Fully compatible with the newest release, [PostgreSQL Version 16.](https://www.postgresql.org/docs/16/index.html)\
> Updated third-party libraries.\
> Send any issues encountered during instance monitoring directly to the platform.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.datasentinel.io/manual/implementation/agent-usage/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.