The Redrock Postgres development team is pleased to announce Redrock Postgres version 3.2, which is based on the PostgreSQL 17 community release.
Redrock Postgres is an enterprise-grade distribution of PostgreSQL, focusing on the quality and stability of database, and is fully compatible with all features and capabilities of the PostgreSQL community edition.
For more information, please see the website.
Feature overview:
No table bloat issue; No need for regular heavyweight vacuum of tables and indexes; Transaction IDs in 64-bit format, eliminating the need for regular full freezing of whole cluster data; Logging records for rolling back modified data and transactions, making transaction status maintenance and management simpler and more stable.
The Redrock Postgres development team is pleased to announce Redrock Postgres version 3.1, which is based on the PostgreSQL 17.4 community release.
Redrock Postgres is an enterprise-grade distribution of PostgreSQL, focusing on the quality and stability of database, and is fully compatible with all features and capabilities of the PostgreSQL community edition.
For more information, please see the website.
Feature overview:
No table bloat issue; No need for regular heavyweight vacuum of tables and indexes; Transaction IDs in 64-bit format, eliminating the need for regular full freezing of whole cluster data; Logging records for rolling back modified data and transactions, making transaction status maintenance and management simpler and more stable.
The Redrock Postgres development team is pleased to announce Redrock Postgres version 3.0, which has been synchronized with the latest version of the PostgreSQL community.
Redrock Postgres is an enterprise-grade distribution of PostgreSQL, focusing on the quality and stability of database, and is fully compatible with all features and capabilities of the PostgreSQL community edition.
For more information, please see the website.
Feature overview:
No table bloat issue; No need for regular heavyweight vacuum of tables and indexes; Transaction IDs in 64-bit format, eliminating the need for regular full freezing of whole cluster data; Logging records for rolling back modified data and transactions, making transaction status maintenance and management simpler and more stable.
This release contains a variety of fixes from 2.4-1. For information about new features in major release 2, see Release 2.1.
Migration to Version 2.5 A dump/restore is not required for those running 2.X.
Changes Adjust interfaces to update/delete tuples of system catalogs for DDL operation, to make them same as system catalog access interface in PostgreSQL. Adjust interfaces to update/delete table rows for the executor, to make them same as table access methods in PostgreSQL.
This release contains a variety of fixes from 2.3-1. For information about new features in major release 2, see Release 2.1.
Migration to Version 2.4 A dump/restore is not required for those running 2.X.
Changes Fixed a concurrency issue between the threaded backends and signal handler thread on windows. Fixed a issue that parallel query blocked occasionally on windows. Fixed the issue that minor version upgrade occurred error on windows, although it is just a result of wrong status checking.
This release contains a variety of fixes from 2.2-1. For information about new features in major release 2, see Release 2.1.
Migration to Version 2.3 A dump/restore is not required for those running 2.X.
Changes Fixed the connection issue in hot standby when manages database objects, and the issue in hot standby when performs index scan to access deleted records. Fixed a replication issue when redoing the INSERT and UPDATE operations to extend a new page.
This release contains a variety of fixes from 12.1.5-1. For information about new features in major release 12, see Release 12.1.0.
Migration to Version 2.2 A dump/restore is not required for those running 12.1.X.
Changes Integrate dependent components into software packages, eliminating the dependency on other packages. Revert file name changes in the data directory, including: postmaster.pid, postmaster.opts, postgresql.auto.conf. Released generic packages that supports the RPM format, supports x86 and ARM 64-bit hardware architectures.
This release contains a variety of fixes from 12.1.4-1. For information about new features in major release 12, see Release 12.1.0.
Migration to Version 12.1.5 A dump/restore is not required for those running 12.1.X.
Changes Remove the dependency of the Debian software package on postgresql-common and postgresql-client-common. Adjust the installation on Debian system, detach the database initialization steps, and perform them separately after the user installs the program. Adjust the installation directory on Debian system and install the main program files to the path /usr/pgsql-12.
This release contains a variety of fixes from 12.1.3-1. For information about new features in major release 12, see Release 12.1.0.
Migration to Version 12.1.4 A dump/restore is not required for those running 12.1.X.
Changes Exclude some errors cause transaction level abort. Refactor configuration implementaion related to session variables. Disable update_process_title when threaded_execution enabled. Fix shared_preload_libraries issues and some bugs when threaded_execution enabled. Fix issue when logical decoding DELETE operation. Fix replication issue when redo COPY FROM operation.
This release contains a variety of fixes from 12.1.2-1. For information about new features in major release 12, see Release 12.1.0.
Migration to Version 12.1.3 A dump/restore is not required for those running 12.1.X.
Changes Removed support for the ALTER DATABASE TABLESPACE command. You cannot specify the TABLESPACE option in CREATE DATABASE command. The database owner check and access control permission check can be performed only on the current database. You can use VACUUM command to scan and clean data pages in tables and update the free space map.
