pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Extension-specific version release notes?
3+ messages / 3 participants
[nested] [flat]

* Extension-specific version release notes?
@ 2022-09-20 18:32 PG Doc comments form <noreply@postgresql.org>
  2022-09-20 18:40 ` Re: Extension-specific version release notes? Andrew Grossman <agrossman@songtrust.com>
  0 siblings, 1 reply; 3+ messages in thread

From: PG Doc comments form @ 2022-09-20 18:32 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org; +Cc: agrossman@songtrust.com

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/14/citext.html
Description:

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.


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Extension-specific version release notes?
  2022-09-20 18:32 Extension-specific version release notes? PG Doc comments form <noreply@postgresql.org>
@ 2022-09-20 18:40 ` Andrew Grossman <agrossman@songtrust.com>
  2022-09-20 23:11   ` Re: Extension-specific version release notes? Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Andrew Grossman @ 2022-09-20 18:40 UTC (permalink / raw)
  To: agrossman@songtrust.com; pgsql-docs@lists.postgresql.org

Ah, I see that that information is probably retrievable from the source
code commit info. It might still be helpful to have a version history for
an extension in the docs.

On Tue, Sep 20, 2022 at 2:33 PM PG Doc comments form <noreply@postgresql.org>
wrote:

> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/citext.html
> Description:
>
> 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.
>


-- 

*ANDREW GROSSMAN*
Engineering Manager | SONGTRUST
he | him
|  songtrust.com
|  agrossman@songtrust.com
[image: FB | Songtrust] <https://www.facebook.com/songtrust/; [image:
Tiktok | Songtrust] <https://www.tiktok.com/@songtrust?lang=en; [image: IG
| Songtrust] <http://instagram.com/songtrust; [image: Linked In | Songtrust]
<https://www.linkedin.com/company/songtrust/; [image: Twitter | Songtrust]
<http://twitter.com/songtrust; [image: Youtube | Songtrust]
<http://youtube.com/songtrust;

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Extension-specific version release notes?
  2022-09-20 18:32 Extension-specific version release notes? PG Doc comments form <noreply@postgresql.org>
  2022-09-20 18:40 ` Re: Extension-specific version release notes? Andrew Grossman <agrossman@songtrust.com>
@ 2022-09-20 23:11   ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2022-09-20 23:11 UTC (permalink / raw)
  To: Andrew Grossman <agrossman@songtrust.com>; +Cc: pgsql-docs@lists.postgresql.org

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





^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2022-09-20 23:11 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-09-20 18:32 Extension-specific version release notes? PG Doc comments form <noreply@postgresql.org>
2022-09-20 18:40 ` Andrew Grossman <agrossman@songtrust.com>
2022-09-20 23:11   ` Tom Lane <tgl@sss.pgh.pa.us>

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