# PostgreSQL news PostgreSQL news This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## pgAdmin 4 v9.18 Released DevFeed: [pgAdmin 4 v9.18 Released]() Original publisher: [Read original article]() Author: Pgadmin Development Team Published: 2026-09-17T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [releases](), [Security](), [Vulnerabilities](), [Authentication](), [PostgreSQL](), [GUI](), [vs-code](), [React]() Tags: [2026](), [announce](), [authentication-bypass](), [bug-fixes](), [cve](), [database](), [react](), [security](), [security-vulnerabilities](), [vs-code]() ### AI overview The pgAdmin Development Team announces pgAdmin 4 version 9.18, a release containing 29 bug fixes and new features, including fixes for four security vulnerabilities. Changes include Object Explorer improvements, a hardened Content-Security-Policy, and fixes for authentication bypass and connection-string or argument injection issues in database-management tools. ### Source excerpt The pgAdmin Development Team is pleased to announce the release of pgAdmin 4 version 9.18. This release of pgAdmin 4 includes 29 bug fixes and new features, including fixes for four security vulnerabilities (CVE-2026-86861 through CVE-2026-86864). For more details, please see the release notes. pgAdmin is the leading open-source graphical management tool for PostgreSQL. For more information, please see the website. Notable changes in this release include: Features Collapse and restore the Object Explorer by re-clicking the current workspace icon, in the manner of the VS Code side bar, remembering the choice across refreshes. A keyboard shortcut, Ctrl+Alt+B by default, does the same thing and can be changed through the new toggle_object_explorer preference. Harden the default Content-Security-Policy so inline scripts run under a per-request nonce rather than a blanket 'unsafe-inline', and drop 'unsafe-eval'. style-src keeps 'unsafe-inline', because MUI and React inject runtime styles and inline style attributes that cannot carry a nonce, and development bundles have 'unsafe-eval' re-added automatically when DEBUG is set. Security Fixes Fix an authentication bypass in Webserver authentication mode, where get_user() fell back to reading the configured WEBSERVER_REMOTE_USER name from the inbound request headers when it was absent from the WSGI environment. Because a header is written by whoever sends the request, any client that could reach pgAdmin could assert any identity, including an administrator's, without presenting a credential. A header-asserted identity is now opt-in, restricted to a configured list of trusted proxies with an optional shared secret, and refused for accounts whose authentication source is not webserver (CVE-2026-86863). Fix argument and connection-string injection in the Backup tool, where the client-supplied database name was appended to the pg_dump argument vector as a bare positional value. Because getopt_long permutes arguments, a value beg ## pgAssistant 3.8.0 : continuous improvement loop for Postgres DevFeed: [pgAssistant 3.8.0 : continuous improvement loop for Postgres]() Original publisher: [Read original article]() Author: Pgassistant Dev Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [Monitoring](), [recommendations](), [configuration](), [real-time]() Tags: [configuration](), [measurements](), [monitoring](), [postgres](), [postgresql](), [real-time](), [recommendations](), [release]() ### AI overview pgAssistant 3.8.0 expands the PostgreSQL analysis and tuning tool into a continuous improvement platform. It adds historical workload and environment measurements, compares consecutive collections, tracks recommendations and configuration changes, and helps teams measure changes while distinguishing correlation from causation. ### Source excerpt With this release, pgAssistant is evolving beyond PostgreSQL analysis and tuning to become a continuous PostgreSQL improvement platform. The new positioning is built around a continuous improvement loop: Observe -> Diagnose -> Prioritize -> Plan -> Implement -> Collect again -> Measure pgAssistant already helped identify what should be improved and turn recommendations into a prioritized Executive Plan with clear DEV and OPS ownership. Combined with pgAssistant Collector, version 3.8.0 goes further by adding historical workload and environment measurements. The objective is to answer four essential questions: What should we improve? What did we decide to do? What did we actually change? What was the result? Workload Insights compares consecutive collections and highlights: new and no-longer-detected recommendations; changes to the PostgreSQL version and configuration; workload evolution by statement type; changes in execution time and call volume; the queries with the greatest impact on the overall workload. The ambition is to correlate the application of pgAssistant recommendations and the Executive Plan with observed performance changes. Correlation is not causation, and a recommendation that is no longer detected does not necessarily prove that it was implemented. pgAssistant keeps these distinctions explicit while bringing the relevant evidence together in one place. pgAssistant is not intended to replace real-time monitoring. Monitoring shows what is happening now; pgAssistant helps teams decide what to improve next, organize the remediation work, and measure what changed afterwards. From recommendations to action--and from action to measurable evidence. pgAssistant 3.8.0: https://github.com/beh74/pgassistant-community pgAssistant Collector: https://github.com/beh74/pgassistant-collector pgAssistant Grafana : https://github.com/beh74/pgassistant-grafana ## CERN PGDay 2027: Announcement and CfP DevFeed: [CERN PGDay 2027: Announcement and CfP]() Original publisher: [Read original article]() Author: Swiss PostgreSQL Users Group Published: 2026-09-11T00:00:00Z Content type: news Language: en Sources: [PostgreSQL news]() Topics: [Databases](), [Machine learning](), [AI search](), [Retrieval Augmented Generation (RAG)]() Tags: [announcement](), [community](), [conference](), [database](), [postgresql]() ### AI overview CERN PGDay 2027 is an announcement and call for papers for a single-day PostgreSQL community conference at CERN in Geneva. Proposed talk themes include large-scale database performance, AI and vector-search workloads, security, and PostgreSQL extensibility. ### Source excerpt CERN PGDay 2027 Date: Friday, February 12, 2027 Location: CERN Campus, Geneva, Switzerland / Suisse Romande Language: English Organizers: Swiss PostgreSQL Users Group (SwissPUG) & CERN Format: Single-track (6-7 sessions) followed by networking social event Homepage: swisspug.org/cern-pgday-2027 About the Event Continuing in the line of work of the past editions, CERN PGDay 2027 returns as the annual gathering for PostgreSQL users, developers, and enthusiasts across Suisse Romande (western Switzerland) and the neighboring French border regions. Co-organized by CERN and SwissPUG, this single-day community conference offers a premier opportunity to network, share practical experiences, and explore the future of the world's most advanced open-source database. The event takes place in the unique, international environment of Geneva--a hub for major scientific institutions, non-governmental organizations, and financial and tech enterprises. Format & Venue Single-Track Schedule: The program consists of a single track featuring 6 to 7 technical sessions presented entirely in English. Social Event & Networking: Following the technical presentations, a social event will take place to facilitate community networking, discussions, and collaboration in the inspiring atmosphere of CERN. CERN Visits: Attendees are encouraged to arrange their schedules before or after the event to take advantage of the conference location and visit CERN, the European Organization for Nuclear Research. Call for Papers (CfP) Speaker proposals for CERN PGDay 2027 can be entered online via Indico. Call for Papers Closes: November 8, 2026 (23:59 CET) Call for Sponsors (CfS) Sponsors proposals for CERN PGDay 2027 are welcome. Please find the contract with all details online. Key Themes We welcome talk proposals covering broader PostgreSQL and community trends and localized enterprise & scientific topics: High-Performance Science & Big Data: Managing massive datasets, extreme write throughput, partitioning ## PostgreSQL Migrator 1.0 : first stable release DevFeed: [PostgreSQL Migrator 1.0 : first stable release]() Original publisher: [Read original article]() Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [migration](), [Databases](), [releases](), [MySQL](), [Oracle Database](), [ci]() Tags: [ci](), [migration](), [mysql](), [open-source](), [oracle](), [postgresql](), [release]() ### AI overview PostgreSQL Migrator 1.0 is the first stable release of an open-source tool for migrating Oracle, MySQL, and MariaDB databases to PostgreSQL. It supports full inspection and limited conversion and migration for selected database objects, with compatibility promised across 1.x releases. ### Source excerpt Paris, 7th september 2026. The Dalibo team is pleased to announce the release of PostgreSQL Migrator 1.0 stable, a free and open-source tool designed to help migrate databases from Oracle and MySQL/MariaDB to PostgreSQL. Key features Easy installation: pure Go binary with zero proprietary dependencies. Fast, offline inspection: Extract the full source catalog once, then iterate on conversion offline. Complexity scoring: Quickly assess and compare the difficulty of migration projects. Interactive web UI: Browse both the original and converted catalogs, search objects, and identify migration blockers. Schema and data conversion: Converts datatype and SQL expression, convert column to boolean. Code analysis and transpilation: Transpiles and analyzes SQL, PL/SQL and routines with the companion transqlate tool. High-performance data copy: Streamed bulk COPY to PostgreSQL (or to files / pipes), with low memory usage and significantly higher throughput than traditional tools in our tests. Hackable & configurable: Reliable JSON catalog data, TOML configuration, and templating for fine-tuning. Supported features PostgreSQL Migrator supports migrating from Oracle Database 11g to 26ai, MySQL 8.4+ and MariaDB 10+ to PostgreSQL 16 up to 19. Version 1.0 has full inspection including jobs, system triggers, etc. However, conversion and migration is limited to role, schema, sequences, table, virtual columns, constraints and indexes. The documentation describes implemented and planned features including views, procedural objects, SQL Server and more. Stability We have built a demanding CI pipeline including end-to-end tests based on Oracle Free container and cypress. This effectively prevents regression and ensure quality. After one year of beta and rc, PostgreSQL Migrator is stable. We'll ensure configuration, CLI and project compatibility for all 1.x releases. License and availability PostgreSQL Migrator is released under the PostgreSQL License. Documentation: https://postgresql-mi ## pg\_vault\_tde v1.7.1 : Transparent Data Encryption for PostgreSQL 17 and 18 DevFeed: [pg\_vault\_tde v1.7.1 : Transparent Data Encryption for PostgreSQL 17 and 18]() Original publisher: [Read original article]() Author: Miriade Srl Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [Encryption](), [Database](), [Cryptography]() Tags: [database](), [encryption](), [postgresql](), [release]() ### AI overview pg_vault_tde 1.7.1 adds transparent AES-256-GCM encryption for PostgreSQL 17 and 18, with externally managed keys and online per-table key rotation. It fixes AAD derivation for out-of-line TOAST values; data written by 1.7.0 or earlier must be exported before upgrading affected tables. ### Source excerpt pg_vault_tde provides Transparent Data Encryption for PostgreSQL 17 and 18. A table access method, encrypted_heap, encrypts every tuple with AES-256-GCM before it reaches the storage manager and decrypts it after it leaves, so applications require no changes. Keys are held outside the database: HashiCorp Vault or OpenBao through the Transit engine, a PKCS#11 token or HSM, or a local PKCS#12 wallet. Data encryption keys are per table and can be rotated online. Requirements are PostgreSQL 17 or 18, OpenSSL 3.x, and the library listed in shared_preload_libraries. The current release is 1.7.1. It corrects the AAD derivation for out-of-line TOAST values, with the consequence that TOAST data written by 1.7.0 or earlier does not authenticate under 1.7.1: affected tables must be exported before the new binary is installed. The procedure is documented in the README. pg_vault_tde is released under the PostgreSQL licence. Sources, documentation and binary .deb and .rpm packages are on GitHub; the distribution is on PGXN. ## PostgreSQL Anonymizer 3.2 : Faster Pseudonymization DevFeed: [PostgreSQL Anonymizer 3.2 : Faster Pseudonymization]() Original publisher: [Read original article]() Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [Databases](), [Extension](), [Vulnerabilities]() Tags: [database](), [extension](), [pii](), [postgresql](), [privacy](), [security](), [vulnerabilities]() ### AI overview PostgreSQL Anonymizer 3.2 adds faster localized pseudonymization functions, deprecates the previous pseudo_* functions, and fixes three critical privilege-escalation vulnerabilities. ### Source excerpt Eymoutiers, France, Septembre 4th, 2026 Dalibo is pleased to announce PostgreSQL Anonymizer 3.2 introducing a new panel of fast pseudonymization filters. Enhanced Privacy Protection for Your Data PostgreSQL Anonymizer is an extension that hides or replaces personally identifiable information (PII) or commercially sensitive data from a PostgreSQL database. The extension offers 6 different masking strategies: Dynamic Masking - Real-time data protection Static Masking - Permanent data transformation Replica Masking - Anonymized logical replication Backup Masking - Privacy-protected database exports Masking Views - Controlled data visibility Masking Data Wrappers - Extended protection across systems Each strategy is complemented by an enhanced suite of Masking Functions, including advanced techniques such as: Substitution, Randomization, Faking, Pseudonymization, Partial Scrambling, Shuffling, Noise Addition and Generalization. The extension can be installed with Debian and RPM packages, an Ansible role, a Docker image, etc. You can use it on most major DBaaS providers including : Alibaba Cloud, Crunchy Bridge, Google Cloud SQL, IBM Cloud, Microsoft Azure Database, Neon, Yandex It is also available on some Postgres forks such as EDB Advanced Postgres, Greenplum and Yugabyte. See the INSTALL section of the documentation for more details! Fast and Localized pseudonymization Although Pseudonymization is not Anonymization, it may be useful in some contexts. Until version 3.1, this was achieved with a panel of pseudo_* functions, such as anon.pseudo_last_name(...), anon.pseudo_email(...), etc. These functions are now replaced by a new panel of anon.seeded_* functions, such as anon.seeded_last_name(...), anon.seeded_email(...), etc. The anon.seeded_* functions have 2 main advantages over the previous ones: They can be localized, e.g anon.seeded_street_name(id,'fr_FR') They are 40x faster :) The anon.pseudo_* functions are kept for backward compatibility but are now deprecated ## Autobase 2.11 released DevFeed: [Autobase 2.11 released]() Original publisher: [Read original article]() Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [postgresql clusters](), [Database](), [releases](), [Ansible Roles](), [cloud-infrastructure]() Tags: [ansible](), [cloud](), [operations](), [postgresql](), [postgresql-clusters](), [release]() ### AI overview Autobase 2.11 adds Platform UI management for PostgreSQL cluster scaling, minor and major upgrades, backups, and point-in-time recovery. It also introduces Ansible playbooks for backup and recovery operations. ### Source excerpt Autobase 2.11 is an important milestone in the evolution of the platform. Two years ago, we started working on a broader goal: evolve the Autobase Console from a PostgreSQL deployment UI into a platform for managing the complete cluster lifecycle. With this release, the remaining major pieces of that roadmap are now in place - scaling, upgrades, backups, and point-in-time recovery can all be managed directly from the Platform UI. See the full details in the release notes. Highlights Scaling (read replicas) Scale PostgreSQL read capacity directly from the UI. Simply specify the desired number of cluster nodes, and Autobase will provision the additional replicas automatically using the existing cloud configuration. For cloud deployments, the required servers and related infrastructure resources are created automatically. You can also scale clusters running on your own bare-metal or virtual machines. Start with a single-node PostgreSQL cluster and add replicas later as your workload grows. Upgrades Autobase Platform now supports minor upgrades within the current PostgreSQL major version as well as major-version upgrade workflows. For minor upgrades, replicas are updated one at a time, followed by a switchover and upgrade of the former primary. Read traffic remains available throughout the process, while expected write downtime is only ~5-10 seconds. For in-place major upgrades, the expected downtime is typically ~30-60 seconds. A blue-green major upgrade workflow with near-zero downtime is planned for a future release. Backup & Restore (PITR) Backup and recovery management is now available directly in the Platform UI. Configure the backup method, storage, retention, and schedule, or create backups on demand. Restore options include: Latest: recover to the latest available state Point in time: restore to a specific date and time Specific backup: restore from a selected backup New Ansible playbooks Autobase 2.11 adds new Ansible playbooks for backup and recovery operatio ## PGConf India 2027 - Dates Announced and CFP Open DevFeed: [PGConf India 2027 - Dates Announced and CFP Open]() Original publisher: [Read original article]() Author: PGConf India Published: 2026-09-05T00:00:00Z Content type: news Language: en Sources: [PostgreSQL news]() Topics: [data](), [Replication]() Tags: [cloud](), [community](), [conference](), [data](), [data-platforms](), [disaster-recovery](), [monitoring](), [open-source](), [performance](), [postgres](), [security]() ### AI overview PGConf India 2027 will take place in Bengaluru from March 2-5, 2027. Its Call for Papers is open, with submissions due October 15, 2026, covering PostgreSQL topics including internals, performance, replication, cloud infrastructure, security, monitoring, production case studies, data platforms, extensions, and open source. ### Source excerpt Hey there, Mark your calendars: PGConf India 2027 is set for March 2-5, 2027 at the Sheraton Grand Hotel at Brigade Gateway, Bengaluru. The Call for Papers is open right now. Important dates CFP closes -- October 15, 2026 We tell you yes/no -- November 15, 2026 The actual conference -- March 2-5, 2027 What we're into Basically anything Postgres, including but not limited to: Core internals & features Performance & query tuning HA, replication & disaster recovery Cloud & infra Security & compliance Monitoring & ops Real production case studies ML, analytics & data platforms (pgvector fans, this means you) Extensions & ecosystem tools Community & open source To submit Give us a title, session length (25 or 40 min), your bio, and an abstract (≤500 words) on what you'll say and what people should walk away with. Submit your talk Ticket sales aren't open yet -- watch pgconf.in for that and everything else. See you in Bengaluru. The PGConf India Team https://pgconf.in Powered By ConfBase.io ## pg\_statviz 1.2 released with PostgreSQL 19 support and new features DevFeed: [pg\_statviz 1.2 released with PostgreSQL 19 support and new features]() Original publisher: [Read original article]() Author: Pg Statviz Project Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [Monitoring](), [Time Series](), [Artificial Intelligence](), [API](), [OpenAI](), [Claude]() Tags: [ai](), [ai-models](), [api](), [claude](), [features](), [monitoring](), [openai](), [postgresql](), [release](), [series]() ### AI overview pg_statviz 1.2 adds PostgreSQL 19 support, a blocking-locks analysis module, OpenAI API integration, and updated default Claude and Gemini models. It remains a lightweight PostgreSQL extension and utility for analyzing and visualizing internal statistics, with optional AI features. ### Source excerpt Just in time for the PostgreSQL 19 betas, I'm excited to announce release 1.2 of pg_statviz, the minimalist extension and utility pair for time series analysis and visualization of PostgreSQL internal statistics. This release adds support for the upcoming PostgreSQL 19: pg_statviz now captures the new wal_fpi_bytes counter from pg_stat_wal. The PG18/19 I/O worker, effective WAL level, and autovacuum scoring settings are captured in snapshot_conf. The release has been tested against 19 beta3, and across the whole PostgreSQL 13 to 19 range. It also introduces a new blocking locks analysis module: Each snapshot now records the number of blocked and blocking sessions, along with a breakdown by lock type (relation, transactionid, tuple, and so on). Detection is built on pg_blocking_pids(), so even soft blocks (sessions that are just ahead in the lock wait queue) are counted, not just hard conflicts. Storage stays lightweight: table size is independent of how many sessions were involved in the blocking. The module produces charts and AI verdicts like every other module, and the deterministic severity floor applies here too: sustained blocking can never be reported as healthy. Also new is the openai AI provider: --ai openai uses the OpenAI API, so the same flag works with OpenAI itself and with any other service or local server that implements that API. You can select the endpoint and model with the OPENAI_BASE_URL and OPENAI_MODEL environment variables. The openai package has been added to the [ai] extras, and zero-dependency installs remain unchanged. Finally, this release also updates the default AI models to claude-sonnet-5 for Claude and gemini-3.7-flash for Gemini. pg_statviz takes the view that everything should be light and minimal. Unlike commercial monitoring platforms, it doesn't require invasive agents or open connections to the database: it all lives inside your database. The extension is plain SQL and PL/pgSQL and doesn't require modules to be loaded, the vis ## LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser DevFeed: [LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser]() Original publisher: [Read original article]() Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [ide](), [SQL](), [browser](), [Open Source](), [API](), [Authentication](), [OpenID connect (OIDC)](), [Authorization](), [Back end]() Tags: [api](), [authentication](), [backend](), [browser](), [ide](), [monitoring](), [open-source](), [postgresql](), [release](), [self-hosted](), [sql]() ### AI overview LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and can be deployed as a container, Helm chart, or npm package. The article describes its database-aware query editing, transaction controls, schema introspection, monitoring, optional query assistant, and local-account or OIDC authentication with role-based access control. Release 0.12.0 is highlighted. ### Source excerpt LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and deploys as a container or Helm chart. It is deployed next to the database it manages, as a container, a Helm chart or an npm package, rather than installed on each developer's machine. PostgreSQL is its reference implementation: the provider is built on node-postgres, and the other supported engines follow the patterns established there. On a PostgreSQL connection the editor uses pooled connections, explicit BEGIN/COMMIT/ROLLBACK transactions with an auto-rollback timeout, and query cancellation through pg_cancel_backend on the tracked backend PID. Schema introspection is written to stay responsive on databases with hundreds of tables: the table tree renders from a first pass while relationships stream in from a second. Monitoring reads the pg_stat_* views, including pg_stat_statements where the extension is installed, and degrades to what the connected role can actually see instead of failing when superuser-only views are unavailable. The optional query assistant is constrained by the database rather than by prompt text. A run is given the real schema of the connected database before its first turn, so a drafted statement names objects that exist, and read-only runs execute inside BEGIN READ ONLY as a single statement over the extended protocol. Authentication is local accounts or OIDC, with role-based access control in front of every API route. The current release is 0.12.0. Source, documentation and the PostgreSQL provider reference are at github.com/libredb/libredb-studio and libredb.org. ## Loongson loong64 packages on apt.postgresql.org DevFeed: [Loongson loong64 packages on apt.postgresql.org]() Original publisher: [Read original article]() Author: Apt Postgresql Org Published: 2026-08-19T00:00:00Z Content type: news Language: en Sources: [PostgreSQL news]() Topics: [apt](), [PostgreSQL](), [cpu](), [Geographic Information System](), [Exception]() Tags: [apt](), [architecture](), [community](), [postgresql]() ### AI overview apt.postgresql.org now provides PostgreSQL packages for the Loongson loong64 architecture. The GIS package stack is still awaiting the next PostGIS release. ### Source excerpt We have a new architecture on apt.postgresql.org: Loongson loong64, a Chinese processor architecture. The build host for the architecture is running on a Loongson 3B6000 board provided by the loongfans.cn community. Bootstrapping the PostgreSQL packages was completed earlier this month and everything is in place to be used via apt.postgresql.org. The exception is the GIS stack of packages (postgis, pgrouting, mobilitydb, pgsql-ogr-fdw) which are currently still waiting for the next postgis release. Enjoy, Christoph ## powa-archivist 5.3.0 is out! DevFeed: [powa-archivist 5.3.0 is out!]() Original publisher: [Read original article]() Published: 2026-08-17T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [releases](), [benchmarking](), [monitor](), [Graphs](), [real-time](), [GitHub]() Tags: [bugs](), [changelog](), [contributors](), [documentation](), [github](), [graphs](), [metrics](), [monitor](), [performance](), [postgresql](), [real-time](), [release](), [releases]() ### AI overview The PoWA team announces powa-archivist 5.3.0, a PostgreSQL Workload Analyzer extension that collects and aggregates metrics from multiple PostgreSQL instances, provides real-time charts and graphs for monitoring and tuning servers, and suggests index optimizations. The release also includes a fix for PostgreSQL 19 compatibility. ### Source excerpt Tainan, Taiwan - Sun 16 Aug 2026 powa-archivist 5.3.0 The PoWA team is pleased to announce the release of the version 5.3.0 of powa-archivist, the core extension of the PoWA project. PoWA (PostgreSQL Workload Analyzer) is a performance tool, compatible with all supported PostgreSQL versions. It allows to collect and aggregate metrics gathered from multiple PostgreSQL instances using various extensions covering all parts of PostgreSQL and provides real-time charts and graphs to help monitor and tune your servers. It also suggest optimizations, like global or per-query index suggestions, to easily improve performances. Misc Fix pg19 compatibility with pg19beta2 pg_stat_lock.wait_time datatype change (Julien Rouhaud) Links & Credits Thank to the users who reported bugs or submitted patches, they are all cited in the CHANGELOG file and the CONTRIBUTORS file. powa-archivist is an open project. Any contribution to build a better tool is welcome. You just have to send your ideas, features requests or patches using the github repository at github.com/powa-team/powa-archivist. Links Documentation: powa.readthedocs.io/ Download: github.com/powa-team/powa-archivist/releases Bug tracker: github.com/powa-team/powa-archivist/issues