PostgreSQL news

openHalo Project is now Released!

Wed, 02 Apr 2025 00:00:00 +0000

openHalo provides the capability to migrate MySQL to PostgreSQL with ZERO code change and provides much more better performance than MySQL!

Migrating from legacy MySQL databases can be time-consuming and resource-intensive. When migrating your databases there is often more work to do to migrate the application itself, including re-writing application code that interacts with the database.

openHalo understands the SQL dialect of MySQL, and supports the same communications protocol, so your apps that were originally written for MySQL can work with openHalo with zero or fewer code changes. As a result, the effort required to modify and move applications running on MySQL 5.7 or newer to openHalo is reduced, leading to faster, lower-risk, and more cost-effective migrations.

The project official site is: https://www.openhalo.org and the project is published on GitHub: https://github.com/HaloTech-Co-Ltd/openHalo

Autobase 2.2.0 released

Thu, 27 Mar 2025 00:00:00 +0000

We’re excited to announce the release of Autobase 2.2.0 — packed with valuable improvements and new capabilities:

TLS support across all cluster components — for secure, encrypted communication
ARM architecture support — run Autobase on even more hardware platforms
Automated backups to Hetzner Object Storage (S3) — streamlined disaster recovery
Netdata monitoring out of the box — gain instant visibility into your cluster’s health
Plus a wide range of performance and stability enhancements under the hood

See the full list of changes in the release notes

About Autobase

Autobase for PostgreSQL® is an open-source alternative to cloud-managed databases (DBaaS) like Amazon RDS, Google Cloud SQL, and Azure Database.

It enables you to deploy and manage production-grade, highly available PostgreSQL clusters with ease. Autobase simplifies operations, reduces infrastructure costs, and brings powerful automation to teams — even those without deep DBA expertise.

It automates deployment, failover, backups, restores, upgrades, scaling, and more — eliminating the need for manual database management.

Website: https://autobase.tech

powa-collector 1.3.1 is out!

Tue, 25 Mar 2025 00:00:00 +0000

Taipei, Taiwan - March 23rd, 2025

powa-collector 1.3.1

The PoWA team is pleased to announce the release of the version 1.3.1 of powa-collector, a simple multi-threaded python program that performs the snapshots for all the remote servers configured in a powa repository database.

Changelog

Bugfixes:

Release the savepoints in copy_remote_data_to_repo (Julien Rouhaud, thanks to Thomas Reiss for the report)
Restore compatibility with standard_conforming_strings = off (Julien Rouhaud, thanks to github user rafaelorafaelo for the report)
Properly detect and report missing extensions (Julien Rouhaud, thanks to github users jw1u1 and rafaelorafaelo who both reported the problem)

Credits

Thank to the users who reported bugs or submitted patches, they are all cited in the CHANGELOG file.

powa-collector 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-collector.

Announcing E-Maj 4.6.0.

Mon, 24 Mar 2025 00:00:00 +0000

We are very glad to announce the 4.6.0 version of E-Maj.

E-Maj is a PostgreSQL extension which enables fine-grained write logging and time travel on subsets of the database.

Aside a few bug fixes, this new version brings more flexibility in commenting tables groups and marks. Partitionned tables are also better supported. The Emaj_web client has been improved. In particular, comments can be set on postgres servers, and the Activity page has been enriched.

E-Maj 4.6.0 is compatible with Postgres 11 to 17 versions.

The full documentation is available on line. The core extension is available at pgxn.org for installation or github.org for development.

The Emaj_web client is also available at github.org.

Have fun with E-Maj !

pgtt v4.1 released

Thu, 20 Mar 2025 00:00:00 +0000

Antananarivo, Madagascar - March 18th, 2025

PostgreSQL Global Temporary Tables

pgtt is a PostgreSQL extension to create, manage and use DB2 or Oracle-style Global Temporary Tables. Once created the use is just like with the other RDBMS.

pgtt v4.1 has been released, this is a maintenance release only to fix issues reported by users since latest release.

Complete list of changes is available here

Links & Credits

pgtt 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 tools.

Links :

Documentation: https://github.com/darold/pgtt/
Download: https://github.com/darold/pgtt/releases/
Support: use GitHub report tool at https://github.com/darold/pgtt/issues

About pgtt

The objective of this extension it to provide the Global Temporary Table feature waiting for an in core implementation. The main interest of this extension is to mimic the Oracle behavior with GTT when you can not or don't want to rewrite the application code when migrating to PostgreSQL.

This is a project created and maintained by Gilles Darold at HexaCluster Corp.

pgBadger v13.1 released

Thu, 20 Mar 2025 00:00:00 +0000

Antananarivo, Madagascar - March 17th, 2025

pgBadger

pgBadger is a PostgreSQL performance analyzer, built for speed with fully detailed reports based on your PostgreSQL log files.

pgBadger 13.1 was released today, this release fixes issues reported by users since last release and adds some new features:

Add new report about vacuum throughput with a graph about vacuum per table that consume the more CPU. The table output reports I/O timing read and write per table as well as the CPU time elapsed on the table. This patch also adds frozen pages and tuples to the Vacuums per Table report.
Add --no-fork option for debugging purpose to not fork processes at all.
Add millisecond to the raw csv output.
Add log filename to sample reports when multiple file are processed.

For the complete list of changes, please checkout the release note on https://github.com/darold/pgbadger/releases

Links & Credits

I would like to thank all users who submitted patches and users who reported bugs and feature requests, they are all cited the ChangeLog file.

pgBadger 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 tools or directly to pgbadger@darold.net.

Links :

Download: http://pgbadger.darold.net/
Support: use GitHub report tool at https://github.com/darold/pgbadger/issues or contact pgbadger@darold.net.

For a complete list of commercial support near of your place take a look at the PostgreSQL Professional Services page, they all do great job and most of them can help you.

About pgBadger :

pgBagder is a new generation log analyzer for PostgreSQL, created by Gilles Darold (also author of ora2pg, the powerful migration tool). pgBadger is a fast and easy tool to analyze your SQL traffic and create HTML5 reports with dynamics graphs. pgBadger is the perfect tool to understand the behavior of your PostgreSQL servers and identify which SQL queries need to be optimized.

Docs, Download & Demo at http://pgbadger.darold.net/

IvorySQL 4.4 Released - Based on PostgreSQL 17.4 with Enhanced Platform Support

Tue, 18 Mar 2025 00:00:00 +0000

Dear Community,

We are pleased to announce the release of IvorySQL 4.4, based on PostgreSQL 17.4. This release includes important bug fixes and introduces significant platform support enhancements, along with new documentation features to improve the user experience.

IvorySQL 4.4 Highlights

Expanded Platform Support

ARM64 Packaging (#729): Complete multi-platform media packages for ARM architecture, supporting domestic and international operating systems including Red Hat, Debian, Kylin, UOS, and NSAR OS
X86 Packaging (#735): Expanded multi-platform media packages for X86 architecture with similar comprehensive OS support

Enhanced Documentation

New Kernel Architecture Documentation Framework (#739): Introduces detailed design documentation starting with Oracle compatibility components
Dual Parser Architecture Analysis (#740): In-depth exploration of the dual parser design principles in the Oracle compatibility framework
initdb Architecture Analysis (#741): Detailed explanation of initdb implementation within the Oracle compatibility framework

Improved User Experience

Interactive Chat Feature (#742, #133): The IvorySQL official website now includes a DeepSeek R1 enabled chat room function for intelligent interactions and Q&A about IvorySQL

Bug Fixes

Fixed incomplete SQL generation when using invisible columns with pg_dump (#731)
Addressed installation package issues for EulerOS (#745)
Incorporated all PostgreSQL 17.3 and 17.4 bug fixes

Source Code Access

IvorySQL database source code: https://github.com/IvorySQL/IvorySQL

Official Website

Home https://www.ivorysql.org
Document https://docs.ivorysql.org
Email Groups https://lists.ivorysql.org

For complete details, please visit our documentation site for the full release notes.

We encourage you to download and test this new release. Your feedback is invaluable in helping us continue to improve IvorySQL.

Thank you for your continued support.

Best regards,

The IvorySQL Team

About IvorySQL

IvorySQL is an open-source database project initiated by Highgo Software that extends PostgreSQL with Oracle compatibility features. It provides an ideal solution for users seeking PostgreSQL's robustness while maintaining Oracle compatibility, facilitating easier database migrations. IvorySQL is designed for applications ranging from small-scale projects to large enterprise systems, with a commitment to community-driven development.

Greenmask 0.2.6 - 0.2.8 Releases

Tue, 18 Mar 2025 00:00:00 +0000

PostgreSQL database anonymization and synthetic data generation tool

Greenmask Overview

Greenmask is a powerful open-source utility that is designed for logical database backup dumping, anonymization, synthetic data generation and restoration. It is stateless and does not require any changes to your database schema. It is designed to be highly customizable and backward-compatible with existing PostgreSQL utilities, fast and reliable.

Is perfect for:

Backup and Restoration: Streamline daily tasks like logical backups, table restoration after truncation, or replacing pg_dump and pg_restore with ease.
Anonymization and Data Masking: Simplify staging environment setup and analytical tasks by anonymizing and transforming backups, ensuring consistent, secure data for faster

Greenmasks has Database subset feature - One of the most advanced subset systems on the market. It supports virtual references, nullable columns, polymorphic references, and can subset even the most complex schemas with cyclic references.

Changes

Support postgres:// schema connection URLs #263
Implemented --blobs and --no-blobs flags for the greenmask dump command. These flags allow inclusion or exclusion of large objects in the dump file. By default, --blobs is enabled. If --no-blobs is specified, large object data will be skipped, and only large object creation commands and ACLs will be included in the dump. #265
Implemented the --no-blobs flag for greenmask restore. If there are any large objects in your database, this will create an empty placeholder instead. #265
Enabled support for all textual data types in all transformers that have a text type #267. Closes #260
Fixed numerous introspection queries that have out of range errors caused by casting OID types to int4 values #264. Closes #265
Refactored the logic of restorers and added test coverage to improve maintainability and stability #268
Fixed domain constraint introspection query #266
Revised documentation according to the latest changes #267
Fixed brew build homebrew-core #206868 Closes #261
Fixed a case when converted directory dump into single file using pg_restore --file=1738263512345.sql is corrupted due to lost semicolon #255
Updated go dependencies #256
Introduces --disable-trigers, --use-session-replication-role-replica and --superuser options for restore command. It allows to disable triggers during data section restore #252. Closes feature request #228
Fix skipping unknown type when silent is true #251

Releases list:

Links

Feel free to reach out to us if you have any questions or need assistance:

pgFormatter v5.6 has been released

Tue, 18 Mar 2025 00:00:00 +0000

Antananarivo, Madagascar - March 17th, 2025

pgFormatter v5.6

pgFormatter, even if not perfect, is the most advanced SQL and PlPgsql code formatter and beautifier dedicated to PostgreSQL. It is provided as a CLI or a CGI program.

This major release fixes issues reported by users since the last release with some improvements and new features.

New options and features:

Add support to pg_vector operator <#>.
Add support for the @? jsonb-jsonpath operator.
Follow the XDG Base Directory Specification by searching configuration file into XDG_CONFIG_HOME/pg_format/config.conf.
Check USERPROFILE env var for Windows.
Add to_reg and reg to function list.
Add missing Perl modules in installation instructions.
Add information about the Perl module to install for the JSON feature.
Expand web capabilities of the app with adding API-like JSON capability to the CGI module. The API can be disabled using the enable_api parameter to the CGI (default: 1).
Add option --redundant-parenthesis to prevent pgFormatter to remove redundant parenthesis in DML.

For the complete list of changes, please checkout the release note on https://github.com/darold/pgFormatter/blob/master/ChangeLog

Links & Credits

Thank to the developers who submitted patches and users who reported bugs and feature requests, they are all cited in the ChangeLog file.

pgFormatter 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 tools.

Links:

Website: https://sqlformat.darold.net/
Download: https://github.com/darold/pgFormatter/releases
Development: https://github.com/darold/pgFormatter
Changelog: https://github.com/darold/pgFormatter/blob/master/ChangeLog

About pgFormatter

pgFormatter is a SQL and PlPgsql formatter/beautifier that supports keywords from SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011 and PostgreSQL specifics keywords. May works with any other databases too. It shares the same code with pgBadger, so any improvement made in the parser is reversed to pgBadger. Tool created and maintained by Gilles Darold.

pgFormatter works on any platform and is available under the PostgreSQL license.

pg_ivm 1.10 released

Fri, 14 Mar 2025 00:00:00 +0000

IVM Development Group is pleased to announce the release of pg_ivm 1.10.

Changes since the v1.9 release include:

Bug Fixes

Fix a failure in DROP EXTENSION (Ishant Bhaskar )

Previously, dropping pg_ivm caused the error "could not open relation with OID ..." due to a hook function that allows DROP TABLE on an IMMV to remove its entry from pg_ivm_immv. Additionally, issuing DROP TABLE concurrently with DROP EXTENSION pg_ivm could result in the same error.
Prevent automatic index creation when using set-returning function (Yugo Nagata)

A unique index was previously created automatically even when a set-returning function appeared in the FROM clause, which led to errors due to key duplication.
Change schema from pg_catalog to pgivm (Yugo Nagata)

Previously, pg_upgrade failed due to permission issues because the pg_ivm_immv catalog was created in pg_catalog. To resolve this, all objects created by pg_ivm have been moved to the pgivm schema, which is now created automatically by pg_ivm.

Breaking Change: This affects compatibility with previous releases. If you want to access objects like the create_immv function as before, you must either qualify them with the pgivm schema or adjust your search_path accordingly.
Fixed view maintenance failures when a column is dropped from a table (Yugo Nagata)

When a table contained a dropped column, incremental view maintenance failed with an error like:

ERROR: could not find attribute 43 in subquery targetlist
Fix potential view inconsistency issues (Yugo Nagata)

Previously, the view contents could become inconsistent with the base tables in the following scenarios:

1) A concurrent transaction modifies a base table and commits before the incremental view maintenance starts in the current transaction.

2) A concurrent transaction modifies a base table and commits before the create_immv or refresh_immv command generates data.

3) Concurrent transactions incrementally update a view with a self-join or modify multiple base tables simultaneously.

These issues have now been resolved to ensure consistency.

About pg_ivm

pg_ivm is an extension module that provides Incremental View Maintenance (IVM) feature.

Incremental View Maintenance (IVM) is a way to make materialized views up-to-date in which only incremental changes are computed and applied on views rather than recomputing. pg_ivm provides a kind of immediate maintenance, in which materialized views are updated immediately after a base table is modified.

Source repository: https://github.com/sraoss/pg_ivm