From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Grossman <agrossman@songtrust.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Extension-specific version release notes?
Date: Tue, 20 Sep 2022 19:11:45 -0400
Message-ID: <933846.1663715505@sss.pgh.pa.us> (raw)
In-Reply-To: <CAONYeaLH1NRgPvUpWHpYu=fz1zfiy8Qy9m1g0ZGoCX=OB63qsg@mail.gmail.com>
References: <166369876645.654.8776727487675624313@wrigleys.postgresql.org>
<CAONYeaLH1NRgPvUpWHpYu=fz1zfiy8Qy9m1g0ZGoCX=OB63qsg@mail.gmail.com>
Andrew Grossman <agrossman@songtrust.com> writes:
>> I'm having difficulty finding version difference information about native
>> extensions. For instance, I have an instance running citext version 1.1 and
>> an update command will take it up to 1.6. I was hoping that I'd see some
>> information about version history specific to the extension on the
>> extension's documentation page, but I don't see any reference to extension
>> versioning.
Well, you could always look at the extension delta scripts and see
what they do :-)
Generally speaking, if an extension has actual user-visible feature
changes, those'll be called out in its section of the release notes
for the PG major release where they appeared. However there are
a lot of cases where we bump an extension's version in order to do
some housekeeping that isn't too interesting on its own. For example,
if you look into citext--1.1--1.2.sql you'll discover that that's
mostly just plastering PARALLEL SAFE annotations on most of the
extension's functions, which was housekeeping that we needed after
introducing parallel query in the core code. But it doesn't seem terribly
useful to document such a thing separately for each affected extension.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, agrossman@songtrust.com, pgsql-docs@lists.postgresql.org
Subject: Re: Extension-specific version release notes?
In-Reply-To: <933846.1663715505@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox