Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.postgresql.org/news.rss

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PostgreSQL news</title><link>https://www.postgresql.org/</link><description>PostgreSQL news</description><atom:link href="https://www.postgresql.org/news.rss" rel="self"/><language>en-us</language><lastBuildDate>Wed, 06 Aug 2025 00:00:00 +0000</lastBuildDate><item><title>Nordic PGDay 2026 is returning to Finland for a day of Postgres
  3. </title><link>https://www.postgresql.org/about/news/nordic-pgday-2026-is-returning-to-finland-for-a-day-of-postgres-3112/</link><description>
  4. &lt;p&gt;&lt;a href="https://2026.nordicpgday.org"&gt;Nordic PGDay&lt;/a&gt; will once again return to Helsinki in March 24, 2026, for a day of PostgreSQL in the land of a thousand lakes. Nordic PGDay is a one-day single track event (with an adjoining sponsor track) focusing on bringing together the Postgres community in the Nordic region. The 2026 event will be the 11th Nordic PGDay and the third time we visit Finland. The conference will be held at the &lt;a href="https://2026.nordicpgday.org/venue/"&gt;Scandic Park Helsiniki&lt;/a&gt; just across from the beautiful Töölö Bay in Helsinki, Finland.&lt;/p&gt;
  5. &lt;p&gt;Our &lt;a href="https://2026.nordicpgday.org/cfp/"&gt;call for papers&lt;/a&gt; will open on September 22 and we look forward to hearing your stories. Just before that, on September 1st, we will also open for &lt;a href="https://2026.nordicpgday.org/sponsors/#levels"&gt;sponsorships&lt;/a&gt; with two levels available at a first come first serve basis.&lt;/p&gt;
  6. &lt;p&gt;We hope to see you in Helsinki in March!&lt;/p&gt;
  7. </description><pubDate>Wed, 06 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/nordic-pgday-2026-is-returning-to-finland-for-a-day-of-postgres-3112/</guid></item><item><title>pg_exporter v1.0.0 Released – Next-Level PG Observability
  8. </title><link>https://www.postgresql.org/about/news/pg_exporter-v100-released-next-level-pg-observability-3073/</link><description>
  9. &lt;p&gt;We’re delighted to announce &lt;a href="https://github.com/pgsty/pg_exporter"&gt;pg_exporter&lt;/a&gt; &lt;a href="https://github.com/pgsty/pg_exporter/releases/tag/v1.0.0"&gt;v1.0&lt;/a&gt;, an advanced open-source Prometheus exporter that takes PostgreSQL observability to the next level.&lt;/p&gt;
  10. &lt;p&gt;Built for DBAs and developers who need deep insight, &lt;strong&gt;pg_exporter&lt;/strong&gt; exposes 600 + metrics—roughly 3 K – 20 K time series per instance — covering core PostgreSQL internals, popular extensions such as TimescaleDB, Citus, pg_stat_statements, pg_wait_sampling, and even pgBouncer, all through a single, fully customizable exporter.&lt;/p&gt;
  11. &lt;p&gt;Unlike other exporters, &lt;strong&gt;pg_exporter&lt;/strong&gt; values customizability: every metric lives in a YAML definition, so you can add, modify, or extend metrics without recompiling. The configuration allows fine-grained control over collection logic — PostgreSQL version branching, caching, timeouts, pre-condition queries, a health-check API, and live reload &amp;amp; replanning are all built in.&lt;/p&gt;
  12. &lt;p&gt;Battle-tested for more than six years in production clusters exceeding 25K+ CPU cores, &lt;strong&gt;pg_exporter&lt;/strong&gt; also powers the &lt;a href="https://pigsty.io/"&gt;Pigsty&lt;/a&gt; observability stack — see it in action in the &lt;a href="https://demo.pigsty.io/"&gt;live demo&lt;/a&gt;.&lt;/p&gt;
  13. &lt;p&gt;Version 1.0 brings a host of new features, including &lt;strong&gt;early support for PostgreSQL 18 — ready even before PG 18 beta release&lt;/strong&gt;. Explore 50 + pre-defined &lt;a href="https://github.com/pgsty/pg_exporter/tree/main/config"&gt;collectors&lt;/a&gt;, or create your own (including app-specific metrics via SQL) simply by adding new configs.&lt;/p&gt;
  14. &lt;p&gt;Enjoy next-level insight into your PostgreSQL ecosystem with &lt;strong&gt;pg_exporter v1.0&lt;/strong&gt;!&lt;/p&gt;
  15. &lt;hr&gt;
  16. &lt;h2&gt;Features&lt;/h2&gt;
  17. &lt;ul&gt;
  18. &lt;li&gt;&lt;strong&gt;Highly Customizable&lt;/strong&gt;: Define almost all metrics through declarative YAML configs&lt;/li&gt;
  19. &lt;li&gt;&lt;strong&gt;Full Coverage&lt;/strong&gt;: Monitor both PostgreSQL (10-18+) and pgBouncer (1.8-1.24+) in single exporter&lt;/li&gt;
  20. &lt;li&gt;&lt;strong&gt;Fine-grained Control&lt;/strong&gt;: Configure timeout, caching, skip conditions, and fatality per collector&lt;/li&gt;
  21. &lt;li&gt;&lt;strong&gt;Dynamic Planning&lt;/strong&gt;: Define multiple query branches based on different conditions&lt;/li&gt;
  22. &lt;li&gt;&lt;strong&gt;Self-monitoring&lt;/strong&gt;: Rich metrics about pg_exporter &lt;a href="https://demo.pigsty.cc/d/pgsql-exporter"&gt;itself&lt;/a&gt; for complete observability&lt;/li&gt;
  23. &lt;li&gt;&lt;strong&gt;Production-Ready&lt;/strong&gt;: Battle-tested in real-world environments across 12K+ cores for 6+ years&lt;/li&gt;
  24. &lt;li&gt;&lt;strong&gt;Auto-discovery&lt;/strong&gt;: Automatically discover and monitor multiple databases within an instance&lt;/li&gt;
  25. &lt;li&gt;&lt;strong&gt;Health Check APIs&lt;/strong&gt;: Comprehensive HTTP endpoints for service health and traffic routing&lt;/li&gt;
  26. &lt;li&gt;&lt;strong&gt;Extension Support&lt;/strong&gt;: &lt;code&gt;timescaledb&lt;/code&gt;, &lt;code&gt;citus&lt;/code&gt;, &lt;code&gt;pg_stat_statements&lt;/code&gt;, &lt;code&gt;pg_wait_sampling&lt;/code&gt;,...&lt;/li&gt;
  27. &lt;/ul&gt;
  28. </description><pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/pg_exporter-v100-released-next-level-pg-observability-3073/</guid></item><item><title>PGDay Austria schedule is online &amp;amp; Don&amp;#x27;t miss the Database Deathmatch
  29. </title><link>https://www.postgresql.org/about/news/pgday-austria-schedule-is-online-dont-miss-the-database-deathmatch-3110/</link><description>
  30. &lt;p&gt;Summertime is almost over — kick off the autumn conference season with PGDay Austria! Don’t miss the Database Celebrity Deathmatch, a fully scripted showdown where PostgreSQL takes on its fiercest rivals. We’ve got it all: technical deep dives, drama, a stunning location, and great company!
  31. Okay — on a more serious note…&lt;/p&gt;
  32. &lt;p&gt;PGDay Austria on September 4, 2025
  33. The official conference schedule is now live, featuring a full day of expert sessions, and technical deep dives on PostgreSQL in 3 tracks! — all hosted in the beautiful Apothekertrakt at Schönbrunn Palace in Vienna. Expect sessions on Kubernetes integration, index performance, and replication strategies.
  34. Access the whole schedule: https://pgday.at/schedule/
  35. Alongside the packed agenda, there’s a strong social program to connect with the PostgreSQL community during breaks and networking options after the event.&lt;/p&gt;
  36. &lt;p&gt;Register now for a ticket: www.pgday.at
  37. PS.: Your attendance could help foster an orphaned elephant through the Sheldrick Wildlife Trust. It’s a beautiful way to combine technology, community, and making a positive difference for wildlife.&lt;/p&gt;
  38. &lt;p&gt;Thank you all for supporting this community event and gathering!
  39. Best regards,
  40. The PGDay Austria Organizers Team,
  41. Patricia, Ilya, Cornelia &amp;amp; Hans&lt;/p&gt;
  42. </description><pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/pgday-austria-schedule-is-online-dont-miss-the-database-deathmatch-3110/</guid></item><item><title>Pigsty 3.6, the meta-distribution for PostgreSQL
  43. </title><link>https://www.postgresql.org/about/news/pigsty-36-the-meta-distribution-for-postgresql-3111/</link><description>
  44. &lt;p&gt;The Pigsty team is thrilled to announce &lt;strong&gt;Pigsty v3.6&lt;/strong&gt;, our latest step toward a true &lt;strong&gt;meta-PostgreSQL distribution&lt;/strong&gt;.  From a single code base you can now launch near 10 distinct PostgreSQL kernels — Babelfish, IvorySQL, OpenHalo, OrioleDB, PolarDB, Supabase-PG, Citus, the brand-new &lt;strong&gt;Percona TDE&lt;/strong&gt;, and more.&lt;/p&gt;
  45. &lt;ul&gt;
  46. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/postgres"&gt;PostgreSQL&lt;/a&gt; : Vanilla PostgreSQL with 420+ extensions&lt;/li&gt;
  47. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/citus"&gt;Citus&lt;/a&gt;         : Distributive PostgreSQL via native extension&lt;/li&gt;
  48. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/babelfish"&gt;WiltonDB&lt;/a&gt;  : SQL Server wire-compatibility&lt;/li&gt;
  49. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/ivorysql"&gt;IvorySQL&lt;/a&gt;   : Oracle Grammar and PL/SQL compatible&lt;/li&gt;
  50. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/openhalo"&gt;OpenHalo&lt;/a&gt;   : MySQL wire-protocol compatibility&lt;/li&gt;
  51. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/percona"&gt;Percona&lt;/a&gt;     : Percona Patched PG with pg_tde&lt;/li&gt;
  52. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/ferretdb"&gt;FerretDB&lt;/a&gt;   : MongoDB wire-protocol compatibility&lt;/li&gt;
  53. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/orioledb"&gt;OrioleDB&lt;/a&gt;   : PG without bloat, "cloud-native" with S3 Storage&lt;/li&gt;
  54. &lt;li&gt;&lt;a href="https://doc.pgsty.com/pgsql/kernel/polardb"&gt;PolarDB&lt;/a&gt;     : RAC flavor Postgres&lt;/li&gt;
  55. &lt;li&gt;&lt;a href="https://doc.pgsty.com/app/supabase"&gt;Supabase&lt;/a&gt;            : BaaS upon PostgreSQL&lt;/li&gt;
  56. &lt;/ul&gt;
  57. &lt;p&gt;Each kernel is wrapped as a production-ready, RDS-style service: HA with Patroni, PITR via pgBackRest, deep observability with Grafana / Prometheus, and fully repeatable infrastructure-as-code -- all without Docker or Kubernetes. Materialized with idemopent ansible playbooks on bare Linux.&lt;/p&gt;
  58. &lt;p&gt;This release also introduces a standalone extension catalog (&lt;a href="https://ext.pgsty.com"&gt;ext.pgsty.com&lt;/a&gt;, &lt;strong&gt;423&lt;/strong&gt; build-tested packages) and a completely rebuilt documentation site (&lt;a href="https://doc.pgsty.com"&gt;doc.pgsty.com&lt;/a&gt;).&lt;/p&gt;
  59. &lt;hr&gt;
  60. &lt;h3&gt;Built for PostgreSQL 18 (and friends)&lt;/h3&gt;
  61. &lt;p&gt;Templates, exporters, and client tooling are ready for &lt;strong&gt;PostgreSQL 18 Beta2&lt;/strong&gt;, while versions 17.5, 16.9, 15.13, 14.18, and 13.21 remain fully supported.  Percona TDE and OrioleDB 1.5 β12 bring our supported-kernel count into double digits.&lt;/p&gt;
  62. &lt;h3&gt;Three-step install, one-command PITR&lt;/h3&gt;
  63. &lt;p&gt;Online installation is now the default; it just takes three steps to install everything:&lt;/p&gt;
  64. &lt;p&gt;&lt;code&gt;bash
  65. curl -fsSL https://repo.pigsty.cc/get | bash -s v3.6.0; cd ~/pigsty &amp;amp;&amp;amp; ./configure &amp;amp;&amp;amp; ./install.yml&lt;/code&gt;&lt;/p&gt;
  66. &lt;p&gt;Need to rewind the clock?  The new &lt;code&gt;pgsql-pitr&lt;/code&gt; playbook handles everything automatically — even on multi-node HA clusters. just supply the target timestamp, XID, or LSN, and it does the rest.&lt;/p&gt;
  67. &lt;h3&gt;Supabase hardening &amp;amp; modern observability&lt;/h3&gt;
  68. &lt;p&gt;Pigsty tracks the latest Supabase containers, fixes Logflare replication-slot bloat, and wires up pgsodium keys by default.  The monitoring stack moves to &lt;strong&gt;Grafana 12 + Prometheus 3.5&lt;/strong&gt;, with tuned OS profiles for NVMe servers and an optional plain-HTTP mode for MinIO.&lt;/p&gt;
  69. &lt;h3&gt;423 packaged extensions (and counting)&lt;/h3&gt;
  70. &lt;p&gt;Highlights include &lt;strong&gt;pgactive 2.1.5&lt;/strong&gt;, TimescaleDB 2.21, Citus 13.1, FerretDB 2.4, DuckDB 1.3.2, and the new &lt;strong&gt;genai-toolbox&lt;/strong&gt;.  Browse the catalog or run &lt;code&gt;pig install &amp;lt;name&amp;gt;&lt;/code&gt; to get started.&lt;/p&gt;
  71. &lt;h3&gt;Cleaner roles, clearer switches&lt;/h3&gt;
  72. &lt;p&gt;Destructive Etcd and MinIO actions are now isolated in dedicated &lt;code&gt;*-rm&lt;/code&gt; playbooks, bucket/user provisioning is fully declarative, defaults are rationalised (&lt;code&gt;/data/postgres&lt;/code&gt;, &lt;code&gt;/data/backups&lt;/code&gt;), and self-signed-cert validity is controlled by a single variable—resulting in fewer surprises and smoother rolling upgrades.&lt;/p&gt;
  73. &lt;hr&gt;
  74. &lt;p&gt;Pigsty 3.6 tarballs and architecture-specific offline package sets are available now.  This is the final stop before 4.0 — look forward to PostgreSQL 18 GA support, a vector-based log shipper, and a unified CLI that fronts every playbook.&lt;/p&gt;
  75. &lt;blockquote&gt;
  76. &lt;p&gt;Release Note: https://doc.pgsty.com/release/latest/&lt;/p&gt;
  77. &lt;/blockquote&gt;
  78. </description><pubDate>Mon, 04 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/pigsty-36-the-meta-distribution-for-postgresql-3111/</guid></item><item><title>CloudNativePG 1.26.1, 1.25.3 and 1.27.0-rc1 Released!
  79. </title><link>https://www.postgresql.org/about/news/cloudnativepg-1261-1253-and-1270-rc1-released-3109/</link><description>
  80. &lt;p&gt;The &lt;strong&gt;CloudNativePG Community&lt;/strong&gt; is excited to announce the release of &lt;strong&gt;CloudNativePG Operator&lt;/strong&gt; versions &lt;strong&gt;1.26.1&lt;/strong&gt; and &lt;strong&gt;1.25.3&lt;/strong&gt;—important maintenance updates focused on bug fixes and stability enhancements to keep your PostgreSQL clusters running smoothly in production.&lt;/p&gt;
  81. &lt;p&gt;We strongly recommend all users upgrade to these latest versions to take advantage of the improvements.&lt;/p&gt;
  82. &lt;p&gt;At the same time, we’re introducing &lt;strong&gt;1.27.0-rc1&lt;/strong&gt;, the first &lt;strong&gt;release candidate&lt;/strong&gt; of the upcoming minor version. This preview gives you early access to several notable features, including dynamic loading of PostgreSQL extensions, logical decoding slot synchronization, primary isolation checks, and experimental failover quorum.&lt;/p&gt;
  83. &lt;p&gt;Your feedback will help shape the final release of 1.27.0, expected in the coming weeks.&lt;/p&gt;
  84. &lt;p&gt;Read the full release notes for details:&lt;/p&gt;
  85. &lt;ul&gt;
  86. &lt;li&gt;&lt;a href="https://cloudnative-pg.io/documentation/1.26/release_notes/v1.26/"&gt;Release notes for 1.26.1&lt;/a&gt;&lt;/li&gt;
  87. &lt;li&gt;&lt;a href="https://cloudnative-pg.io/documentation/1.25/release_notes/v1.25/"&gt;Release notes for 1.25.3&lt;/a&gt;&lt;/li&gt;
  88. &lt;li&gt;&lt;a href="https://cloudnative-pg.io/documentation/preview/release_notes/v1.27/"&gt;Release notes for 1.27.0-rc1&lt;/a&gt;&lt;/li&gt;
  89. &lt;/ul&gt;
  90. &lt;p&gt;Thank you for your continued support and for being part of the CloudNativePG
  91. community!&lt;/p&gt;
  92. &lt;p&gt;&lt;em&gt;This release is dedicated to the memory of our dear contributor
  93. &lt;a href="https://www.linkedin.com/in/codepope/"&gt;DJ Walker-Morgan&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
  94. &lt;hr&gt;
  95. &lt;h2&gt;Upgrade Recommendations&lt;/h2&gt;
  96. &lt;ul&gt;
  97. &lt;li&gt;
  98. &lt;p&gt;&lt;strong&gt;Version 1.26.1:&lt;/strong&gt; We strongly recommend upgrading to this version promptly
  99.  to benefit from the latest improvements.&lt;/p&gt;
  100. &lt;/li&gt;
  101. &lt;li&gt;
  102. &lt;p&gt;&lt;strong&gt;Version 1.25.3:&lt;/strong&gt; For users on version 1.25, updating to 1.25.3 is
  103.  essential for continued stability and support. Please note that support for
  104.  version 1.25 will conclude on &lt;strong&gt;August 22, 2025&lt;/strong&gt;.&lt;/p&gt;
  105. &lt;/li&gt;
  106. &lt;/ul&gt;
  107. &lt;p&gt;Before proceeding with the upgrade, ensure you review the
  108. &lt;a href="https://cloudnative-pg.io/documentation/1.26/installation_upgrade/#upgrading-to-126-from-a-previous-minor-version"&gt;upgrade instructions&lt;/a&gt;
  109. carefully.&lt;/p&gt;
  110. &lt;hr&gt;
  111. &lt;h2&gt;Join Our Community&lt;/h2&gt;
  112. &lt;p&gt;&lt;a href="https://github.com/cloudnative-pg/cloudnative-pg?tab=readme-ov-file#communications"&gt;Connect with our community on your preferred platform&lt;/a&gt;!&lt;/p&gt;
  113. &lt;p&gt;If you're using CloudNativePG in production, consider
  114. &lt;a href="https://github.com/cloudnative-pg/cloudnative-pg/blob/main/ADOPTERS.md"&gt;adding your organization as an adopter&lt;/a&gt;
  115. to support the project's growth and evolution.&lt;/p&gt;
  116. &lt;h2&gt;About CloudNativePG&lt;/h2&gt;
  117. &lt;p&gt;&lt;a href="https://cloudnative-pg.io"&gt;CloudNativePG&lt;/a&gt; is an open-source Kubernetes
  118. Operator specifically designed for PostgreSQL workloads. It manages the entire
  119. lifecycle of a PostgreSQL cluster, including bootstrapping, configuration, high
  120. availability, connection routing, and comprehensive backup and disaster
  121. recovery mechanisms. By leveraging PostgreSQL's native streaming replication,
  122. CloudNativePG efficiently distributes data across pods, nodes, and zones using
  123. standard Kubernetes patterns, enabling seamless scaling of replicas in a
  124. Kubernetes-native manner. Originally developed and supported by
  125. &lt;a href="https://www.enterprisedb.com/"&gt;EDB&lt;/a&gt;, CloudNativePG is a CNCF Sandbox project
  126. and the sole PostgreSQL operator in this category.&lt;/p&gt;
  127. </description><pubDate>Thu, 31 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/cloudnativepg-1261-1253-and-1270-rc1-released-3109/</guid></item><item><title>pgAdmin 4 v9.6 Released
  128. </title><link>https://www.postgresql.org/about/news/pgadmin-4-v96-released-3108/</link><description>
  129. &lt;p&gt;The pgAdmin Development Team is pleased to announce pgAdmin 4 version 9.6. This release of pgAdmin 4 includes 4 new features and 7 bug fixes/housekeeping changes. For more details, please see the &lt;a href="https://www.pgadmin.org/docs/pgadmin4/9.6/release_notes_9_6.html"&gt;release notes&lt;/a&gt;.&lt;/p&gt;
  130. &lt;p&gt;pgAdmin is the leading Open Source graphical management tool for PostgreSQL. For more information, please see &lt;a href="https://www.pgadmin.org/"&gt;the website&lt;/a&gt;.&lt;/p&gt;
  131. &lt;p&gt;Notable changes in this release include:&lt;/p&gt;
  132. &lt;h3&gt;Features:&lt;/h3&gt;
  133. &lt;ul&gt;
  134. &lt;li&gt;Ensure that keyboard shortcuts are displayed in tooltips, context menus, and the main menu.&lt;/li&gt;
  135. &lt;li&gt;Implemented a server-side cursor to enhance performance when retrieving large datasets.&lt;/li&gt;
  136. &lt;li&gt;Added support for setting a custom SESSION_DIGEST_METHOD in pgAdmin 4 to facilitate FIPS compliance.&lt;/li&gt;
  137. &lt;li&gt;Enable the PKCE workflow for OAuth 2 authentication.&lt;/li&gt;
  138. &lt;/ul&gt;
  139. &lt;h3&gt;Bugs/Housekeeping:&lt;/h3&gt;
  140. &lt;ul&gt;
  141. &lt;li&gt;Fixed an issue where windows installer is not signing tmp files generated by InnoSetup.&lt;/li&gt;
  142. &lt;li&gt;Fixed an issue in the Search Objects tool where selecting a node occasionally selected an incorrect node.&lt;/li&gt;
  143. &lt;li&gt;Improved the application state restoration by leveraging rc-dock layout and ensure the order and layout of tabs is maintained on restore.&lt;/li&gt;
  144. &lt;li&gt;Fixed an issue where json editor in result grid was crashing if null value is set in the json editor.&lt;/li&gt;
  145. &lt;li&gt;Update zstd library link to 1.5.7 in Dockerfile.&lt;/li&gt;
  146. &lt;li&gt;Ensure that pgAdmin 4 is compatible with PG/EPAS v18.&lt;/li&gt;
  147. &lt;li&gt;Use 'Drop' instead of 'Delete' for object commands to make destructive actions more deliberate.&lt;/li&gt;
  148. &lt;/ul&gt;
  149. &lt;p&gt;Builds for Windows and macOS are available now, along with a Python Wheel, Docker Container, RPM, DEB Package, and source code tarball from the &lt;a href="https://www.pgadmin.org/download/"&gt;download area&lt;/a&gt;.&lt;/p&gt;
  150. </description><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/pgadmin-4-v96-released-3108/</guid></item><item><title>PGDay Napoli 2025, Schedule and Registration
  151. </title><link>https://www.postgresql.org/about/news/pgday-napoli-2025-schedule-and-registration-3105/</link><description>
  152. &lt;p&gt;We're pleased to announce that we published the schedule of the PGDay Napoli taking place in Naples, Italy, on September 25, 2025.&lt;/p&gt;
  153. &lt;p&gt;This day-long event is packed with engaging talks by industry experts, covering a wide range of PostgreSQL topics.&lt;/p&gt;
  154. &lt;p&gt;Check out the exciting line-up and secure your spot:&lt;/p&gt;
  155. &lt;p&gt;Schedule: &lt;a href="https://www.postgresql.eu/events/pgdaynapoli2025/schedule"&gt;https://www.postgresql.eu/events/pgdaynapoli2025/schedule&lt;/a&gt;&lt;/p&gt;
  156. &lt;p&gt;Registration: &lt;a href="https://2025.pgdaynapoli.org/registration"&gt;https://2025.pgdaynapoli.org/registration&lt;/a&gt;&lt;/p&gt;
  157. &lt;p&gt;Don't miss this opportunity to learn from the best, network with fellow PostgreSQL enthusiasts, and contribute to the vibrant PostgreSQL community.&lt;/p&gt;
  158. &lt;p&gt;We can't wait to see you in Naples!&lt;/p&gt;
  159. </description><pubDate>Tue, 22 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/pgday-napoli-2025-schedule-and-registration-3105/</guid></item><item><title>Autobase 2.3.0 released
  160. </title><link>https://www.postgresql.org/about/news/autobase-230-released-3104/</link><description>
  161. &lt;p&gt;We’re thrilled to announce Autobase &lt;a href="https://github.com/vitabaks/autobase/releases/tag/2.3.0"&gt;2.3.0&lt;/a&gt; — a new major release that brings new features, essential improvements, and deeper integration capabilities. &lt;/p&gt;
  162. &lt;h3&gt;What's new&lt;/h3&gt;
  163. &lt;ul&gt;
  164. &lt;li&gt;
  165. &lt;p&gt;&lt;strong&gt;Dark Theme in the Console UI&lt;/strong&gt;&lt;/p&gt;
  166. &lt;p&gt;One of the most requested features is here — a beautiful dark mode for the Autobase Console. A more comfortable and modern experience, especially for those late-night sessions!&lt;/p&gt;
  167. &lt;/li&gt;
  168. &lt;li&gt;
  169. &lt;p&gt;&lt;strong&gt;Import Existing Clusters&lt;/strong&gt;&lt;/p&gt;
  170. &lt;p&gt;You can now import existing clusters into the Autobase UI — for example, those previously deployed via CLI — and instantly gain a visual overview and monitoring of the cluster’s state.&lt;/p&gt;
  171. &lt;/li&gt;
  172. &lt;li&gt;
  173. &lt;p&gt;&lt;strong&gt;Export Clusters to Ansible Inventory&lt;/strong&gt;&lt;/p&gt;
  174. &lt;p&gt;Autobase now supports exporting clusters to an Ansible inventory file directly from the UI. This is perfect for switching to a &lt;a href="https://autobase.tech/docs/management/gitops"&gt;CI/CD&lt;/a&gt;-driven workflow after visual deployment.&lt;/p&gt;
  175. &lt;/li&gt;
  176. &lt;li&gt;
  177. &lt;p&gt;&lt;strong&gt;Ansible Collection&lt;/strong&gt;&lt;/p&gt;
  178. &lt;p&gt;We’ve refactored the automation system into a modern &lt;a href="https://github.com/vitabaks/autobase/blob/master/automation/README.md"&gt;Ansible Collection&lt;/a&gt;. This makes it easier than ever to integrate Autobase into your own infrastructure projects.&lt;/p&gt;
  179. &lt;/li&gt;
  180. &lt;li&gt;
  181. &lt;p&gt;&lt;strong&gt;AWS Network Load Balancer (NLB)&lt;/strong&gt;&lt;/p&gt;
  182. &lt;p&gt;We’ve added support for AWS Network Load Balancer — a high-performance, low-latency option for handling large volumes of traffic efficiently in production environments.&lt;/p&gt;
  183. &lt;/li&gt;
  184. &lt;/ul&gt;
  185. &lt;p&gt;This release includes many additional fixes, performance improvements, and quality-of-life updates, all aimed at making Autobase even more stable, efficient, and user-friendly.
  186. See the full list of changes in the &lt;a href="https://github.com/vitabaks/autobase/releases/tag/2.3.0"&gt;release notes&lt;/a&gt;&lt;/p&gt;
  187. &lt;h2&gt;About Autobase&lt;/h2&gt;
  188. &lt;p&gt;&lt;strong&gt;Autobase&lt;/strong&gt; is an open-source, self-hosted DBaaS (database-as-a-service) platform for PostgreSQL.&lt;/p&gt;
  189. &lt;p&gt;It empowers you to deploy and manage production-grade, highly available PostgreSQL clusters with ease. Autobase simplifies operations, reduces infrastructure costs, and brings powerful automation to your team — even without deep DBA expertise.&lt;/p&gt;
  190. &lt;p&gt;Automate deployment, failover, backups, restores, upgrades, scaling, and more — eliminating the need for manual database management.&lt;/p&gt;
  191. &lt;p&gt;Website: &lt;a href="https://autobase.tech"&gt;https://autobase.tech&lt;/a&gt;&lt;/p&gt;
  192. </description><pubDate>Mon, 21 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/autobase-230-released-3104/</guid></item><item><title>Isok -- a PostgreSQL extension for query based data integrity management
  193. </title><link>https://www.postgresql.org/about/news/isok-a-postgresql-extension-for-query-based-data-integrity-management-3102/</link><description>
  194. &lt;p&gt;&lt;a href="https://kop.codeberg.page/pg_isok_docs/"&gt;Isok&lt;/a&gt; is PostgreSQL extension for query based data integrity
  195. management.  It is now available for public testing.&lt;/p&gt;
  196. &lt;p&gt;Documentation and installation instructions:
  197. &lt;a href="https://kop.codeberg.page/pg_isok_docs/"&gt;https://kop.codeberg.page/pg_isok_docs/&lt;/a&gt;&lt;/p&gt;
  198. &lt;p&gt;Discover problematic data patterns, track them, and manage them, by
  199. reporting not only the &lt;em&gt;existence&lt;/em&gt; of particular data patterns, but also
  200. by tracking &lt;em&gt;changes&lt;/em&gt; to patterns of data and managing issue resolution.
  201. When configured to accept some questionable rows but not others of the
  202. same kind, Isok acts like a "soft trigger".&lt;/p&gt;
  203. &lt;p&gt;Useful for "zero code required" batch-based data validation.  Most
  204. useful when review is required to determine whether a questionable
  205. data pattern should be allowed to remain in a database.&lt;/p&gt;
  206. &lt;p&gt;Although the core Isok code has been in production use for over a
  207. decade, this release has enhanced features that have not been used in
  208. production.&lt;/p&gt;
  209. &lt;p&gt;Isok can be built as pure SQL, for installation in the cloud or other
  210. managed PostgreSQL instances.&lt;/p&gt;
  211. &lt;p&gt;Isok targets PostgreSQL 10 or later.&lt;/p&gt;
  212. </description><pubDate>Sun, 20 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/isok-a-postgresql-extension-for-query-based-data-integrity-management-3102/</guid></item><item><title>PostgreSQL 18 Beta 2 Released!
  213. </title><link>https://www.postgresql.org/about/news/postgresql-18-beta-2-released-3103/</link><description>
  214. &lt;p&gt;The PostgreSQL Global Development Group announces that the second beta release of
  215. PostgreSQL 18 is now &lt;a href="https://www.postgresql.org/download/"&gt;available for download&lt;/a&gt;.
  216. This release contains previews of all features when PostgreSQL 18 is made
  217. generally available, though some details of the release can change during the
  218. beta period.&lt;/p&gt;
  219. &lt;p&gt;You can find information about all of the PostgreSQL 18 features and changes in
  220. the &lt;a href="https://www.postgresql.org/docs/18/release-18.html"&gt;release notes&lt;/a&gt;:&lt;/p&gt;
  221. &lt;p&gt;&lt;a href="https://www.postgresql.org/docs/18/release-18.html"&gt;https://www.postgresql.org/docs/18/release-18.html&lt;/a&gt;&lt;/p&gt;
  222. &lt;p&gt;In the spirit of the open source PostgreSQL community, we strongly encourage you
  223. to test the new features of PostgreSQL 18 on your systems to help us eliminate
  224. bugs and other issues. While we do not advise you to run PostgreSQL 18 Beta 2 in
  225. production environments, we encourage you to find ways to run your typical
  226. application workloads against this beta release.&lt;/p&gt;
  227. &lt;p&gt;Your testing and feedback helps the community ensure that PostgreSQL 18
  228. upholds our standards of delivering a stable, reliable release of the
  229. world's most advanced open source relational database. Please read more about
  230. our &lt;a href="https://www.postgresql.org/developer/beta/"&gt;beta testing process&lt;/a&gt; and how
  231. you can contribute:&lt;/p&gt;
  232. &lt;p&gt;&lt;a href="https://www.postgresql.org/developer/beta/"&gt;https://www.postgresql.org/developer/beta/&lt;/a&gt;&lt;/p&gt;
  233. &lt;h2&gt;Upgrading to PostgreSQL 18 Beta 2&lt;/h2&gt;
  234. &lt;p&gt;To upgrade to PostgreSQL 18 Beta 2 from an earlier version of PostgreSQL,
  235. you will need to use a strategy similar to upgrading between major versions of
  236. PostgreSQL (e.g. &lt;code&gt;pg_upgrade&lt;/code&gt; or &lt;code&gt;pg_dump&lt;/code&gt; / &lt;code&gt;pg_restore&lt;/code&gt;). For more
  237. information, please visit the documentation section on
  238. &lt;a href="https://www.postgresql.org/docs/18/static/upgrading.html"&gt;upgrading&lt;/a&gt;.&lt;/p&gt;
  239. &lt;h2&gt;Changes Since Beta 1&lt;/h2&gt;
  240. &lt;p&gt;Fixes and changes in PostgreSQL 18 Beta 2 include:&lt;/p&gt;
  241. &lt;ul&gt;
  242. &lt;li&gt;Add support for prepared statements in squashing lists in query jumbling.&lt;/li&gt;
  243. &lt;li&gt;Fix for foreign key validation on partitioned tables.&lt;/li&gt;
  244. &lt;li&gt;Remove &lt;code&gt;pg_get_process_memory_contexts()&lt;/code&gt; function.&lt;/li&gt;
  245. &lt;li&gt;Several fixes for injection point testing to support testing AIO.&lt;/li&gt;
  246. &lt;li&gt;Fix &lt;code&gt;pg_dump&lt;/code&gt; for tables with complex names.&lt;/li&gt;
  247. &lt;li&gt;Fix for statement location calculation for nested statements.&lt;/li&gt;
  248. &lt;li&gt;Fix for upgrades from PostgreSQL 14 when the number of rows in a table is
  249. unknown.&lt;/li&gt;
  250. &lt;li&gt;Fix stack overflow for OAuth parsers.&lt;/li&gt;
  251. &lt;li&gt;Set &lt;code&gt;pg_dump&lt;/code&gt; and &lt;code&gt;pg_dumpall&lt;/code&gt; default behavior to use &lt;code&gt;--no-statistics&lt;/code&gt;.
  252. Leave the default for &lt;code&gt;pg_restore&lt;/code&gt; and &lt;code&gt;pg_upgrade&lt;/code&gt; to be &lt;code&gt;--with-statistics&lt;/code&gt;.&lt;/li&gt;
  253. &lt;li&gt;Ensure &lt;code&gt;LOAD $libdir/&lt;/code&gt; works.&lt;/li&gt;
  254. &lt;li&gt;Improvements for GIN amcheck.&lt;/li&gt;
  255. &lt;li&gt;Remove &lt;code&gt;PQservice()&lt;/code&gt; from &lt;code&gt;libpq&lt;/code&gt;.&lt;/li&gt;
  256. &lt;/ul&gt;
  257. &lt;p&gt;Please see the &lt;a href="https://www.postgresql.org/docs/18/release-18.html"&gt;release notes&lt;/a&gt;
  258. for a complete list of new and changed features:&lt;/p&gt;
  259. &lt;p&gt;&lt;a href="https://www.postgresql.org/docs/18/release-18.html"&gt;https://www.postgresql.org/docs/18/release-18.html&lt;/a&gt;&lt;/p&gt;
  260. &lt;h2&gt;Testing for Bugs &amp;amp; Compatibility&lt;/h2&gt;
  261. &lt;p&gt;The stability of each PostgreSQL release greatly depends on you, the community,
  262. to test the upcoming version with your workloads and testing tools to find bugs
  263. and regressions before the general availability of PostgreSQL 18. As this is a
  264. Beta, minor changes to database behaviors, feature details, and APIs are still
  265. possible. Your feedback and testing will help determine the final tweaks on the
  266. new features, so please test in the near future. The quality of user testing
  267. helps determine when we can make a final release.&lt;/p&gt;
  268. &lt;p&gt;A list of &lt;a href="https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items"&gt;open issues&lt;/a&gt;
  269. is publicly available in the PostgreSQL wiki.  You can
  270. &lt;a href="https://www.postgresql.org/account/submitbug/"&gt;report bugs&lt;/a&gt; using this form on
  271. the PostgreSQL website:&lt;/p&gt;
  272. &lt;p&gt;&lt;a href="https://www.postgresql.org/account/submitbug/"&gt;https://www.postgresql.org/account/submitbug/&lt;/a&gt;&lt;/p&gt;
  273. &lt;h2&gt;Beta Schedule&lt;/h2&gt;
  274. &lt;p&gt;This is the second beta release of version 18. The PostgreSQL Project will
  275. release additional betas as required for testing, followed by one or more
  276. release candidates, until the final release around September/October 2025. For further
  277. information please see the &lt;a href="https://www.postgresql.org/developer/beta/"&gt;Beta Testing&lt;/a&gt;
  278. page.&lt;/p&gt;
  279. &lt;h2&gt;Links&lt;/h2&gt;
  280. &lt;ul&gt;
  281. &lt;li&gt;&lt;a href="https://www.postgresql.org/download/"&gt;Download&lt;/a&gt;&lt;/li&gt;
  282. &lt;li&gt;&lt;a href="https://www.postgresql.org/developer/beta/"&gt;Beta Testing Information&lt;/a&gt;&lt;/li&gt;
  283. &lt;li&gt;&lt;a href="https://www.postgresql.org/docs/18/release-18.html"&gt;PostgreSQL 18 Beta Release Notes&lt;/a&gt;&lt;/li&gt;
  284. &lt;li&gt;&lt;a href="https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items"&gt;PostgreSQL 18 Open Issues&lt;/a&gt;&lt;/li&gt;
  285. &lt;li&gt;&lt;a href="https://www.postgresql.org/account/submitbug/"&gt;Submit a Bug&lt;/a&gt;&lt;/li&gt;
  286. &lt;li&gt;&lt;a href="https://www.postgresql.org/about/donate/"&gt;Donate&lt;/a&gt;&lt;/li&gt;
  287. &lt;/ul&gt;
  288. </description><pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.postgresql.org/about/news/postgresql-18-beta-2-released-3103/</guid></item></channel></rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.postgresql.org/news.rss

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda