Skip to content

[pull] development from pgpartman:development#24

Open
pull[bot] wants to merge 148 commits into
jolorunyomi:developmentfrom
pgpartman:development
Open

[pull] development from pgpartman:development#24
pull[bot] wants to merge 148 commits into
jolorunyomi:developmentfrom
pgpartman:development

Conversation

@pull

@pull pull Bot commented Nov 22, 2024

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

keithf4 and others added 30 commits March 30, 2021 15:27
…y acquire an exclusive lock on the original table hence adding CONCURRENTLY (#391)

Co-authored-by: Biran <birayaha@f8ffc21f4dbb.ant.amazon.com>
This used to be `%3$s < %5$L` until v4.6.2, which fixed the %3 but not the %5
keithf4 and others added 30 commits December 20, 2024 12:59
pg_partman uses PL/pgSQL functions but did not declare it as a required
extension. Adding `requires = 'plpgsql'` ensures CREATE EXTENSION works
even if plpgsql was dropped.

Signed-off-by: belo4ya <41exey.kov41ev@gmail.com>
The way the code works prior to this change proposal, is that the transaction open for the final table to have constraints applied, will be left un-commited during the ANALYZE phase. 
Since an ACCESS EXCLUSIVE lock will still be held, this can be problematic.
Improve the `on.push.tags` entry in `.github/workflows/release.yml` to
use a regular expression that matches only non-pre-release semantic
version tags. This should prevent it from releasing a prerelease on
PGXN. It will need refining should the desire arise to put prerelease
versions on PGXN.
)

Fixed incorrect use of comparison operator (=) instead of assignment
operator (:=) in partition_data_time and partition_data_id functions
when processing data in DESC order with batch intervals.

This bug caused variable assignments to be treated as boolean
comparisons that were evaluated and discarded, preventing proper
calculation of partition boundaries when using p_order := 'DESC'.

Affected locations:
- partition_data_time.sql line 252: v_min_partition_timestamp assignment
- partition_data_id.sql line 154: v_min_partition_id assignment (ASC)
- partition_data_id.sql line 168: v_min_partition_id assignment (DESC)
- partition_data_id.sql line 174: v_min_partition_id batch adjustment

This resolves issue #828 where partition_data_proc would fail with
"relation does not exist" errors when called with p_order := 'DESC'
and a p_interval parameter on monthly partitioned tables.
* update changelog

* update changelog

* version 5.4.0 initial commit

* v5.4.0 - fix variable assignment error. add unit test for it.
* fix: allow toast relopt inheritance from template

* update source sql file

* fix wrong variable name. add unit test for relopt inheritance

* update test count for new tests

* adjust relopt test per suggestion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⤵️ pull merge-conflict Resolve conflicts manually

Projects

None yet

Development

Successfully merging this pull request may close these issues.