<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynatrace Hub - PostgreSQL latest releases</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>A list of extensions from PostgreSQL</description><atom:link href="https://hub-manager.hub.central.dynatrace.com/api/v1/public-hub/feed/extensions/postgresdb-remote-monitoring/" rel="self"/><language>en-us</language><lastBuildDate>Wed, 25 Mar 2026 13:04:49 +0000</lastBuildDate><item><title>PostgreSQL 2.9.8</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Revert change from extension version &lt;code&gt;2.9.7&lt;/code&gt; , regarding metric description &amp;amp; graphs for &lt;code&gt;postgres.xid_age&lt;/code&gt;,  to use &lt;code&gt;2^31&lt;/code&gt; instead of &lt;code&gt;2^32&lt;/code&gt; for the wraparound value.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 25 Mar 2026 13:04:49 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.9.6</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Enhancements&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Updated entity links in Platform dashboards to redirect to the Infrastructure and Operations app&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adjusted required dimensions for entity creation to prevent null entities from being created.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 19 Feb 2026 10:49:59 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.9.3</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added an &lt;code&gt;SLRU&lt;/code&gt; feature set with the following metrics:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.blks_zeroed.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.blks_hit.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.blks_read.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.blks_written.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.blks_exists.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.flushes.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.slru.truncates.count&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added an &lt;code&gt;IO&lt;/code&gt; feature set with the following metrics (PG16+):
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.io.reads.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.read_time.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.writes.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.write_time.count &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.writebacks.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.writeback_time.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.extends.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.extend_time.count &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.hits.count &lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.evictions.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.reuses.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.fsyncs.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.fsync_time.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.read_bytes.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.write_bytes.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.io.extend_bytes.count&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added a &lt;code&gt;User Functions&lt;/code&gt; feature set with the following metrics:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.user_functions.calls.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.user_functions.total_time.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.user_functions.self_time.count&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added a &lt;code&gt;Subscription&lt;/code&gt; feature set with the following metrics:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.apply_error.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.sync_error.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_insert_exists.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_update_origin_differs.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_update_exists.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_update_missing.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_delete_origin_differs.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_delete_missing.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.subscription_stats.confl_multiple_unique_conflicts.count&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added the following metrics to the &lt;code&gt;Replication&lt;/code&gt; feature set:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.replication.backend_xmin_age&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.replication.slot_xmin_age&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.replication.replay_delay&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_receiver.last_msg_send_age&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_receiver.last_msg_receipt_age&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_receiver.latest_end_age&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.database_conflicts.tablespace.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.database_conflicts.lock.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.database_conflicts.snapshot.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.database_conflicts.bufferpin.count&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.database_conflicts.deadlock.count&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added the following metrics to the &lt;code&gt;WAL&lt;/code&gt; feature set:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_files_size&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_files&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.wal_files_age&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added the following metric to the &lt;code&gt;Activity&lt;/code&gt; feature set:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.active_waiting&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Adjusted Database activity charts.&lt;/li&gt;
&lt;li&gt;Added feature set descriptions.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 10 Feb 2026 08:11:04 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.8.1</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added Davis Anomaly Detection alert templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed Postgres instance in recovery alert splitting by a non-existing dimension.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 17 Dec 2025 09:19:30 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.7.3</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Postgres Instances can now be viewed from the host page.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed DQL for Query Performance and Blocking Activity in Platform dashboard.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 03 Dec 2025 13:36:15 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.6.5</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where some background writer metrics would not be collected for Postgres 17.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 19 Aug 2025 13:48:55 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.6.3</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added ready-made Platform dashboard.&lt;/li&gt;
&lt;li&gt;Database version is now an attribute of the Postgres instance entities.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 24 Jul 2025 07:47:18 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.5.5</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where the Connection Usage % chart would sometimes show no data.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 28 May 2025 14:51:34 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.5.4</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Database configuration parameters are now monitored as part of the default feature set. By default, this data is fetched every 24 hours, but this can be adjusted with the &lt;code&gt;Configuration query interval (minutes)&lt;/code&gt; variable. This data will be available soon in the Databases App.&lt;/li&gt;
&lt;li&gt;Added a new feature set &lt;code&gt;Replication&lt;/code&gt; which collects replication lag metrics, &lt;code&gt;postgres.replication.*&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Added a new feature set &lt;code&gt;Locks&lt;/code&gt; which collects lock related metrics as well as information about blocking statements in the form of logs.&lt;/li&gt;
&lt;li&gt;A new database size metric is now collected, &lt;code&gt;postgres.db_size&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;In order to monitor transaction wraparound issues, transaction ID age is now collected in the metric &lt;code&gt;postgres.xid_age&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Added a database unreachable alert template.
Note that all alert templates now default to disabled. The recommended approach to use these alerts is to clone them before enabling/changing them.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Enhancements&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Top statements are now associated to the database they correspond to. Block hit/read/dirtied/written counts and read/write times are now collected.&lt;/li&gt;
&lt;li&gt;When possible, top statements are correlated with &lt;code&gt;pg_stat_activity&lt;/code&gt; data to obtain wait event times.&lt;/li&gt;
&lt;li&gt;Additional charts added to various sections of the databases app and entity screens.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ℹ️ This version requires ActiveGate version 1.301.0 or higher.&lt;/p&gt;
</description><pubDate>Wed, 28 May 2025 09:33:33 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.3.4</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When OneAgent monitoring is configured in the database server, a &lt;code&gt;SAME_AS&lt;/code&gt; relationship will be established between the &lt;code&gt;sql:postgres_instance&lt;/code&gt; and the corresponding &lt;code&gt;PROCESS_GROUP_INSTANCE&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ℹ️ This version requires ActiveGate version 1.301.0 or higher.&lt;/p&gt;
</description><pubDate>Tue, 08 Apr 2025 07:28:55 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.3.3</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where the WAL diff size metric would not be collected for replication instances. This metric will now have value 0 instead of null when there is no recovery happening.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ℹ️ This version requires ActiveGate version 1.301.0 or higher.&lt;/p&gt;
</description><pubDate>Tue, 18 Mar 2025 07:12:39 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.3.1</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where the &lt;code&gt;heavy-query-interval&lt;/code&gt; variable's default value would not be set correctly.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 30 Jan 2025 14:37:57 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.3.0</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where top statements would appear duplicated in the Databases app&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There are now two variables which can be defined at the configuration level, &lt;code&gt;query-interval&lt;/code&gt; and &lt;code&gt;heavy-query-interval&lt;/code&gt;, which control the frequency with which the Dynatrace queries the database/ingests data. Please see the FAQ section for more details.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 30 Jan 2025 10:09:28 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.2.6</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed the top queries not showing for certain non-Grail environment in the Postgres Instance screen.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ℹ️ This version requires ActiveGate version 1.293.0 or higher.&lt;/p&gt;
</description><pubDate>Tue, 19 Nov 2024 09:54:15 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.2.5</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Improvements&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Top queries will now no longer collect &lt;code&gt;ALTER&lt;/code&gt; statements for security reasons.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed the Top queries by execution time section in the Databases app.&lt;/li&gt;
&lt;li&gt;Fixed the displayed columns for top statements in the Databases app.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ℹ️ This version requires ActiveGate version 1.293.0 or higher.&lt;/p&gt;
</description><pubDate>Tue, 12 Nov 2024 13:58:38 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.2.2</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;WARNING&lt;/strong&gt; This extension requires minimum ActiveGate version 1.293. Please check your version before upgrading.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed bug where top queries would not be collected from &lt;code&gt;pg_stat_statements&lt;/code&gt; for PostgreSQL 13.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 05 Jul 2024 12:52:48 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.2.1</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;WARNING&lt;/strong&gt; This extension requires minimum ActiveGate version 1.293. Please check your version before upgrading.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;(SaaS only) Added execution plan query support with the database app. For users on SaaS who have access to the Databases app execution plan fetching is now supported. View the &lt;code&gt;Getting started&lt;/code&gt; section on the hub tile for more details on how to set it up.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Mon, 01 Jul 2024 16:13:47 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.1.2</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Query duration as collected by &lt;code&gt;longest_queries&lt;/code&gt; is now calculated as &lt;code&gt;clock_timestamp() - query_start&lt;/code&gt;. Previously it was computed as &lt;code&gt;now() - query_start&lt;/code&gt; which sometimes caused the query duration to be negative.&lt;/p&gt;
&lt;p&gt;The reason behind this is that &lt;code&gt;now()&lt;/code&gt; or &lt;code&gt;CURRENT_TIMESTAMP&lt;/code&gt; represent the start of the transaction and an individual query within the transaction can start later. The &lt;code&gt;clock_timestamp()&lt;/code&gt; however returns an actual system cpu clock and can change over the course of the transaction, producing a correct value to subtract &lt;code&gt;query_start&lt;/code&gt; from to compute a valid duration.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 19 Jun 2024 13:12:41 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 2.1.1</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;&lt;strong&gt;Bug fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;[BREAKING CHANGE]&lt;/strong&gt; Renamed &lt;code&gt;postgres.blk_hit.count&lt;/code&gt; metric key to &lt;code&gt;postgres.blks_hit.count&lt;/code&gt; to match official Postgres statistics collector name.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Features&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added an optional endpoint metadata configuration parameter to each endpoint in the monitoring configuration. This parameter will populate the &lt;code&gt;endpoint_metadata&lt;/code&gt; attribute of &lt;code&gt;sql:postgres_instance&lt;/code&gt; entities and can be used in entity selectors (to facilitate tagging, for example).&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;Queries&lt;/code&gt; feature set will now collect queries (ingested as logs) from the &lt;code&gt;pg_stat_statements&lt;/code&gt; table as well. These new logs can be queried by filtering by &lt;code&gt;event_group = top_queries&lt;/code&gt;. Note that for this to work, the &lt;code&gt;pg_stat_statements&lt;/code&gt; table needs to be enabled at the database level &lt;a href="https://www.postgresql.org/docs/current/pgstatstatements.html#PGSTATSTATEMENTS"&gt;as per the official docs&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Added metric charts to the Postgres instance view in the Databases app.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Improvements&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Aggregated activities from &lt;code&gt;pg_stat_activity&lt;/code&gt; is now collected for all activities, not just the ones associated with a specific &lt;code&gt;datid&lt;/code&gt;. That adds monitoring for activites such as &lt;code&gt;autovacuum worker&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 13 Jun 2024 12:48:20 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item><item><title>PostgreSQL 1.2.0</title><link>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</link><description>&lt;p&gt;Improvements:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Monitoring for databases was improved to support all versions of Postgres starting with 11. Previously, it only worked for Postgres 14+.&lt;/li&gt;
&lt;li&gt;All metrics were linked to their corresponding Entity Type to make sure the metrics are displayed correctly when Management Zones are activated and are filtered by entity.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Bug fixes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;client_port&lt;/code&gt; dimension was removed from the following metrics, because the field bring no valuable information and is too volatile, causing too many distinct timeseries to be generated.
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.active&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.fastpath_function_call&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.idle_in_transaction_aborted&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.idle_in_transaction&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;postgres.activity.idle&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 22 Mar 2024 15:35:05 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/postgresdb-remote-monitoring/</guid></item></channel></rss>