Skip to content

Releases: orioledb/postgres

Pre-release for rewind function

22 May 13:23
Compare
Choose a tag to compare
Pre-release
patches17_8888

Modify CountOtherDBBackends/TerminateOtherDBBackends to process whole…

Pre-release for rewind function

22 May 13:23
Compare
Choose a tag to compare
Pre-release
patches16_8888

Modify CountOtherDBBackends/TerminateOtherDBBackends to process whole…

Version 17_9

28 Apr 13:29
38ff421
Compare
Choose a tag to compare
Merge pull request #14 from orioledb/patches17_deprecate_ubuntu_focal

Use Ubuntu 24.04 image

Version 17_8

28 Apr 11:50
20a0652
Compare
Choose a tag to compare
Support for running PG regress check on tables created with orioledb AM

This creates separate test schedule, fixes regression tests, and patches pg_regress diff params.

Merged pull request #13 from e-ivkov/checkworld

Version 16_36

28 Apr 14:16
Compare
Choose a tag to compare
patches16_36

Remove tests non-existing in PG16 from parallel_schedule_oriole

Version 17_4

06 Nov 13:50
Compare
Choose a tag to compare
Stabilize jsonb_path_query test case.

An operation like '12:34:56'::time_tz takes the UTC offset from
the prevailing time zone, which means that the results change
across DST transitions.  One of the test cases added in ed055d249
failed to consider this.

Per report from Bernhard Wiedemann.  Back-patch to v17, as the
test case was.

Discussion: https://postgr.es/m/[email protected]

Version 16_32

06 Nov 13:39
Compare
Choose a tag to compare
Teach bitmap path generation about transforming OR-clauses to SAOP's

When optimizer generates bitmap paths, it considers breaking OR-clause
arguments one-by-one.  But now, a group of similar OR-clauses can be
transformed into SAOP during index matching.  So, bitmap paths should
keep up.

This commit teaches bitmap paths generation machinery to group similar
OR-clauses into dedicated RestrictInfos.  Those RestrictInfos are considered
both to match index as a whole (as SAOP), or to match as a set of individual
OR-clause argument one-by-one (the old way).

Therefore, bitmap path generation will takes advantage of OR-clauses to SAOP's
transformation.  The old way of handling them is also considered.  So, there
shouldn't be planning regression.

Discussion: https://postgr.es/m/567ED6CA.2040504%40sigaev.ru
Reviewed-by: Alexander Korotkov <[email protected]>

Version 17_3

22 Oct 08:44
Compare
Choose a tag to compare
patches17_3

Fix active snapshot checks

Version 17_2

21 Oct 11:26
Compare
Choose a tag to compare
Revert pre 5bf748b86bc67 SAOP behavior in PG17

Commit 5bf748b86bc67 allows generation of unsafe SAOP path keys
on a multicolumn index that were disabled previously by 807a40c5.

Version 17_1

18 Oct 10:32
Compare
Choose a tag to compare
patches17_1

Fix warning in pg_rewind