Releases: IvorySQL/IvorySQL
IvorySQL 3.2
Version Overview
[Release Date: April 11, 2024]
IvorySQL 3.2, based on PostgreSQL 16.2, introduces Oracle XML function compatibility features along with a variety of bug fixes. For a comprehensive list of updates, please visit our documentation site.
Enhancements
-
Oracle XML Function Compatibility
This Feature integrates compatibility for various Oracle XML functions, including APPENDCHILDXML, DELETEXML, EXISTSNODE, EXTRACT(XML), EXTRACTVALUE, INSERTCHILDXMLAFTER, INSERTCHILDXMLBEFORE, INSERTCHILDXML, INSERTXMLAFTER, INSERTXMLBEFORE and UPDATEXML.
For further details, visit issue #587. -
PostgreSQL 16.2 Enhancements
- Ensure durability of CREATE DATABASE
- Ensure that column default values are correctly transmitted by the pgoutput logical replication plugin
- Re-validate a subscription's connection string before use
- Return the correct status code when a new client disconnects without responding to the server's password challenge
- In PL/pgSQL, support SQL commands that are CREATE FUNCTION/CREATE PROCEDURE with SQL-standard bodies
For further details, visit PostgreSQL’s release notes.
Fixed Issue
- Resolved documentation build failure: Issue #645
- Eliminated build warnings: Issue #649
- Corrected parameter issue with the to_date function: Issue #592
- Fix label issues in create function: Issue #624
Source Code
IvorySQL's development is maintained across two main repositories:
- IvorySQL database source code: https://github.com/IvorySQL/IvorySQL
- IvorySQL official website: https://github.com/IvorySQL/Ivory-www
Contributors
The following individuals (in alphabetical order) have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Bei Fu
- Cary Huang
- David Zhang
- Grant Zhou
- Jiao Ren
- Lei Shang
- Leo X.M. Zeng
- Lily Wang
- Nan Jia
- Shawn Yan
- Shiji Niu
- Shoubo Wang
- Shuntian Jiao
- Xiangyu Liang
- Xinjie Lv
- Xinyuan Guo
- Xiuhua Ruan
- Xueyu Gao
- Ying Huang
- Yonghao Li
- Zheng Liu
IvorySQL 3.1
Version Introduction
[Release Date: January 26, 2024]
IvorySQL 3.1 is based on PostgreSQL 16.1 and includes several bug fixes and improvements from PostgreSQL 16.1. For more detailed list of updates, please refer to the official website PostgreSQL 16.1 Release Notes .
Known Issues
- No issues have been found.
Enhancements
Fixed Issue
Source Code
IvorySQL contains 3 main code repositories, the database IvorySQL code bin, and the IvorySQL blog bin.
- IvorySQL code bin: https://github.com/IvorySQL/IvorySQL
- IvorySQL blog bin: https://github.com/IvorySQL/Ivory-www
Contributors
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Grant Zhou
- Shuntian Jiao
- Shiji Niu
- Xiangyu Liang
- Xueyu Gao
- Cary Huang
- David Zhang
- Yang Tan
- Jie Wang
- Shuainan Mu
- Hongyuan Zhang
- Shoubo Wang
- Jiao Ren
- Zheng Liu
- Zhekai Xiao
- Huajian Jin
- Lily Wang
- Lei Shang
- Lei Feng
- Jinzhou Song
- Leo X.M. Zeng
- Shaoan Yan
- M.Imran Zaheer
- Yunhe Xu
- Hao Wang
- Miss Dong
- Weibo Han
IvorySQL 3.0
Version Introduction
[Release Date: November 17, 2023]
IvorySQL 3.0 is based on PostgreSQL 16.0 includes various fixes from PostgreSQL 16.0, for more detailed updates and bug fixes in PostgreSQL
16.0, please see the official website PostgreSQL 16.0 Release Notes .
Known Issues
- No issues have been found.
Enhancements
Fixed Issue
Source Code
IvorySQL contains 3 main code repositories, the database IvorySQL code bin, and the IvorySQL blog bin.
- IvorySQL code bin: https://github.com/IvorySQL/IvorySQL
- IvorySQL blog bin: https://github.com/IvorySQL/Ivory-www
Contributors
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Pro development & testing team
- Yang Tan
- Jie Wang
- Shuainan Mu
- Hongyuan Zhang
- Cary Huang
- Grant Zhou
- David Zhang
- Shoubo Wang
- Jiao Ren
- Zheng Liu
- Zhekai Xiao
- Huajian Jin
- Lily Wang
- Jinzhou Song
- Leo X.M. Zeng
- Shaoan Yan
- M.Imran Zaheer
- Yunhe Xu
- Hao Wang
- Miss Dong
- Weibo Han
IvorySQL 3.0 beta
Versions Introduction
[Release Date: June 28, 2023]
IvorySQL 3.0 beta is based on PostgreSQL 16 and includes various fixes and new features from IvorySQL 3.0 beta onwards.
This version is compatible with IvorySQL 3.X and does not require a dump/restore for users running IvorySQL 2.X.
IvorySQL 3.0 beta includes various fixes from PostgreSQL 16, including improved sorting performance and compression, logging and configuration enhancements, more fine-tuned logical replication options, and more. For more detailed updates and bug fixes in PostgreSQL 16, see the official https://www.postgresql.org/docs/release/16.0/[PostgreSQL 16.0 Release Notes] .
Known Issues
- No issues have been found.
Enhancements
Fixed issue
Source Code
IvorySQL contains 3 main code repositories, the database IvorySQL code bin, and the IvorySQL blog bin.
- IvorySQL code bin: https://github.com/IvorySQL/IvorySQL[https://github.com/IvorySQL/IvorySQL]
- IvorySQL blog bin: https://github.com/IvorySQL/Ivory-www[https://github.com/IvorySQL/Ivory-www]
Contributors
IvorySQL Release - 2.3
Versions Introduction
[Release Date: June 28, 2023]
IvorySQL 2.3 is based on PostgreSQL 15.3 and includes various fixes and new features from IvorySQL 2.2 onwards.
This version is compatible with IvorySQL 2.X and does not require a dump/restore for users running IvorySQL 1.X.
IvorySQL 2.3 includes various fixes from PostgreSQL 15.3, including improved sorting performance and compression, logging and configuration enhancements, more fine-tuned logical replication options, and more. For more detailed updates and bug fixes in PostgreSQL 15.3, see the official https://www.postgresql.org/docs/release/15.3/[PostgreSQL 15.3 Release Notes] .
Known Issues
- No issues have been found.
Enhancements
- No feature enhancements.
Fixed issue
- No issues fixed.
Source Code
IvorySQL contains 2 main code repositories, the database IvorySQL code bin, and the IvorySQL blog bin.
- IvorySQL code bin: https://github.com/IvorySQL/IvorySQL[https://github.com/IvorySQL/IvorySQL]
- IvorySQL blog bin: https://github.com/IvorySQL/Ivory-www[https://github.com/IvorySQL/Ivory-www]
Contributors
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or issue reporters.
- Cary Huang
- Grant Zhou
- Yang Tan
- Jie Wang
- Shuainan Mu
- Hongyuan Zhang
- Shoubo Wang
- Jiao Ren
- Zhekai Xiao
- Huajian Jin
- Lily Wang
- Songjin Zhou
- M.Imran Zaheer
Stamp IvorySQL 2.2
[Release Date: Mar 29, 2023]
IvorySQL 2.2 is based on PostgreSQL 15.2 and includes various fixes and new features from IvorySQL 2.1 onwards.
This version is compatible with IvorySQL 2.1 and does not require a dump/restore for users running IvorySQL 1.X.
IvorySQL 2.2 includes various fixes from PostgreSQL 15.2, including improved sorting performance and compression, logging and configuration enhancements, more fine-tuned logical replication options, and more. For more detailed updates and bug fixes in PostgreSQL 15.2, see the official [PostgreSQL 15.2 Release Notes]
(https://www.postgresql.org/docs/release/15.2/) .
Contributors
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or issue reporters.
- Yang Tan
- Jie Wang
- Shuainan Mu
- Jingru Bai
- Songjin Zhou
- M.Imran Zaheer
- Huajian Jin
- Zhekai Xiao
- Lily Wang
- Jiao Ren
- Shoubo Wang
- Cary Huang
- David Zhang
- Grant Zhou
IvorySQL Release - 2.1
[Release Date: Dec 14, 2022]
IvorySQL 2.1 is based on PostgreSQL 15.1 and contains a variety of fixes from Postgres community and new feature since IvorySQL 1.5.
New feature: Global unique index
“Global unique index” is a unique index on a partitioned table that can ensure cross-partition uniqueness using a non-partition key. This feature can be used in Postgres and Oracle compatibility modes.
This work is inspired by this email thread, “Proposal: Global Index” started back in 2019. Our team took a different approach to implement the feature that ensures uniqueness constraint spanning multiple partitions without heavy modification to current Postgres’s partitioned table/index structure. In other words, a global unique index and a regular partitioned index are essentially the same in terms of their storage structure except that one can do cross-partition uniqueness check, the other cannot.Global unique index can be created with "GLOBAL" and "UNIQUE" clauses in a "CREATE INDEX" statement run against a partitioned table. For example,
CREATE UNIQUE INDEX global_index ON idxpart(bid) GLOBAL;
With a global unqiue index created, cross partition uniqueness can be guaranteed with INSERT, UPDATE, ATTACH and DETACH operations.
Contributions
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Cary Huang
- David Zhang
- Grant Zhou
IvorySQL Release - 1.5
[Release Date: Sep 09, 2022]
IvorySQL 1.5 is based on PostgreSQL 14.5 and contains a variety of fixes and new feature from IvorySQL 1.4.
This release is compatible with IvorySQL 1.4 and does not require a dump/restore for those running IvorySQL 1.X.
It contains a variety of fixes from 14.4, specifically fixes an issue with Extension scripts replace objects not belonging to the extension that could cause to run arbitrary code as the victim role, which may be a superuser. More details can be found at 14.5 release
Similarly, there are some important fix included:
- Fix replay of CREATE DATABASE WAL records on standby servers
- Support “in place” tablespaces
- Fix permissions checks in CREATE INDEX
For updates and bug fixes in PostgreSQL 14.5 please refer to the official PostgreSQL 14.5 release notes.
Bug Fixes
- Fixed package variables to allow constants and disallow pseudo type variables. Details
- Package tab complete. Details
Contributions
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Asif Rehman
- Grant Zhou
- Shengbin Zhao
- Muhammad Usama
IvorySQL Release - 1.4
[Release Date: Jun 28, 2022]
IvorySQL 1.4 is based on PostgreSQL 14.4 and contains a variety of fixes and new feature from IvorySQL 1.3.
This release is compatible with IvorySQL 1.3 and does not require a dump/restore for those running IvorySQL 1.X.
It contains a variety of fixes from 14.3, specifically fixes an issue with CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY that could cause silent data corruption of indexes. Prior to the fix, CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY could build indexes that would have missing entries, causing SELECT queries that used the index to not find certain rows. More details can be found at 14.4 release
if you have any indexes that were created using the CONCURRENTLY option under 14.X, you should re-index them after updating. See the first changelog entry of PostgreSQL 14.4 release notes
For updates and bug fixes in PostgreSQL 14.4 please refer to the official PostgreSQL 14.4 release notes.
Bug Fixes
- Fixed package privileges issue. Details
Contributions
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Asif Rehman
- Grant Zhou
- Shengbin Zhao
- Muhammad Usama
IvorySQL Release - 1.3
[Release Date: May 27, 2022]
IvorySQL 1.3 is based on PostgreSQL 14.3 and contains a variety of fixes and new feature from IvorySQL 1.1.
This release is compatible with IvorySQL 1.2 and does not require a dump/restore for those running IvorySQL 1.X
However, if you have any GiST indexes on columns of type ltree (supplied by the contrib/ltree extension), you should re-index them after updating to IovrySQL 1.3. See the second changelog entry of PostgreSQL 14.3 release notes
For updates and bug fixes in PostgreSQL 14.3 please refer to the official PostgreSQL 14.3 release notes.
New Features
- Support for Anonymous blocks.
Anonymous are unnamed PL blocks in PL/iSQL. Unlike named blocks, An anonymous block is not get saved in the Database server and is just for one-time use.
Details
Bug Fixes
- Fixed a server crash using the LEVEL pseudo column. Details
- Fixed an issue with using the extended data types in Packages throws an error. Details
- Fixed an issue, If the package is created in pg_catalog namespace (implicitly part of search_path), calling the package object without -schema qualification throws function/procedure not found error. Details
- Fixed an issue with nls_length_semantics is not honored by NCHAR and NVARCHAR Details
- Fixed an issue with DROP PACKAGE BODY not cleaning up the package body Details
- Fixed an issue with specifying END label in PL/iSQL was throwing an error Details
Contributions
The following individuals have contributed to this release as patch authors, committers, reviewers, testers, or reporters of issues.
- Asif Rehman
- Grant Zhou
- Jack Lan
- Shengbin Zhao
- Muhammad Usama