Revisions 381, 382¶
A new revision of Charmed PostgreSQL for Kubernetes has been published in the 14/stable channel.
What’s changed¶
This section outlines the most important highlights, features and bug fixes in this release.
Upgraded PostgreSQL from v.14.11 → v.14.12 ( #563 )
Check the official PostgreSQL release notes
Added support for Point In Time Recovery ( #554 ) (DPE-4839 )
Added COS tracing support with tempo-k8s ( #497 ) (DPE-4617 )
Features¶
Bug fixes¶
Switched test app interface ( #595 )
Added missing
awaittoinvalid_extra_user_rolesintegration test + fix check loop ( #602 )Fixed UTC time zone ( #592 )
Quick fix for blocked CI ( #533 )
Added test for relations coherence ( #505 )
Addressed test_charm and test_self_healing instabilities ( #510 ) (DPE-4594 )
Import JujuVersion from ops.jujuversion instead of ops.model ( #640 )
Don’t block on missing Postgresql version ( #626 ) (DPE-3562 )
Run integration tests on arm64 ( #478 )
Removed deprecated config option
profile-limit-memory( #608 )Block charm if plugin disable fails due to dependent objects ( #567 ) (DPE-4801 )
Temporarily disable log forwarding & fix for race in Patroni REST password setup ( #663 )
Use manifest file to check for charm architecture ( #665 ) (DPE-4239 )
Added log for
fix_leader_annotationmethod ( #679 )
Full Changelog: https://github.com/canonical/postgresql-k8s-operator/compare/rev280…rev381
Known limitations¶
The unit action
resume-upgraderandomly raises a harmless error message :terminated.The charm sysbench may crash during a PostgreSQL charm refresh.
Make sure that cluster-cluster replication is requested for the same charm/workload revisions. An automated check is planned .
Contact us to schedule a cluster-cluster replication upgrade with you.
Requirements¶
The minimum Juju version required to reliably operate all features in this release is v3.4.5.
See the system requirements for more details about Juju versions and other software and hardware prerequisites.