Current version is affected by CVE-2024-4317
Description:
PostgreSQL 16.3 fixed CVE-2024-4317. However, upstream states that:
By itself, this fix will only fix the behavior in newly initdb'd database clusters. If you wish to apply this change in an existing cluster, you will need to do the following:
Maybe a post_upgrade message is good?
Additional info:
Upstream notes: https://www.postgresql.org/docs/release/16.3/