Re: Extension-specific version release notes?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Grossman <agrossman(at)songtrust(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Extension-specific version release notes?
Date: 2022-09-20 23:11:45
Message-ID: 933846.1663715505@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Andrew Grossman <agrossman(at)songtrust(dot)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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2022-09-22 10:53:18 Documentation on pgdump(1) uses "regular expression" instead of "psql pattern"
Previous Message Andrew Grossman 2022-09-20 18:40:04 Re: Extension-specific version release notes?