Is pg_partman 4.8.0 available in dnf repository for Rocky 9.5?

[Piogar]

Hello,

I'm trying to use pg_partman on Rocky 9.5 and Postgres 13 (this won't change for some time for sure). I encountered issue #585 (this will be common sceneario in my system and infinite_time_partitions=true indeed does not create premake partitions when no new data comes), which per my understanding is fixed in versions 5.0.0+ or 4.8.0. I found, that version 5.0.0+ requires Postgres 14, so I wanted to use 4.8.0 (it works with Postgres 13, right?).

Is pg_partman 4.8.0 available in some dnf repository (https://download.postgresql.org/pub/repos/yum/13/redhat/rhel-9.5-x86_64/ contains only version 4.7.4)? If not, is it downloadable as rpm or needs to be built and install from sources?

Thanks in advance,
Piotr

[keithf4]

So I don't control the packaging releases on my end. However, there not being a 4.8.0 package is not a surprise since this was released with version 5.1.0

https://github.com/pgpartman/pg_partman/releases/tag/v5.1.0

The 4.8.0 patch file is available if you install the latest version of pg_partman and you can update specifically to it if you already have 4.7.4 installed.

ALTER EXTENSION pg_partman UPDATE TO '4.8.0';

However, your issue here is not something that was fixed in 4.8.0, only in the 5.1 release. The 4.8.0 release notes are at the bottom of the above release announcement. There likely is not going to be any further work on the 4.x series of partman, especially since PostgreSQL 13 will be going EOL in November of this year. So I would highly recommend looking at getting moved off PG13 sooner than you may have been considering.

https://www.postgresql.org/support/versioning/

[Piogar]

Thank you for quick response. Unfortunately I'm not able to force Postgres version change for whole project, so I'll need to find another solution for that. For now I see either rebuild 4.7.4 pg_partman with cherry-picked fix or implement my own solution for retention.

[keithf4]

Apologies I couldn't help get a fix back into 4.x at this time. Partman has changed quite a lot in 5.x so trying to keep 4.x up to date anymore isn't really feasible at this time. I would recommend finding another solution vs trying to cherry-pick a fix into the extension. That makes it so that when you are able to upgrade to a newer version of PG you can then upgrade partman as well. If you change partman code it may block upgrade attempts.