Thanks Nathan,
Is this the whole guidelines we have for this ?
Did not recognise it at once, but I assume that this implies also
things about backporting, as only way to backport something is to put
it in a minor release.
I was hoping that there were some exceptions possible for things
affecting interactions between different versions that need also
support from older versions, but if this page is all we have then
likely not.
BTW, this is also why I am not entirely happy about logical
replication being part of the core, as this implies that no bigger
improvements are possible for cases when it is used for version
upgrades. Or at least the improvements would be of no use for
upgrading existingdatabases .
Do we have the same strict no improvements in minor versions policy
for contrib/ extensions and tools?
On Wed, Jan 14, 2026 at 10:53 PM Nathan Bossart
<nathandbossart@gmail.com> wrote:
>
> On Wed, Jan 14, 2026 at 10:46:07PM +0100, Hannu Krosing wrote:
> > Do we have clear written guidelines about what can and can not be backported ?
> > And do we distinguish between the core database, extensions and tools for this?
>
> From https://www.postgresql.org/support/versioning:
>
> Minor releases only contain fixes for frequently-encountered bugs,
> low-risk fixes, security issues, and data corruption problems.
>
> --
> nathan
