Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released! - Mailing list pgsql-advocacy

From Jonathan S. Katz
Subject Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released!
Date
Msg-id 7f58a703-e810-95d2-489a-06d1788cd357@postgresql.org
Whole thread Raw
In response to Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released!  (Michael Banck <michael.banck@credativ.de>)
Responses Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released!
List pgsql-advocacy
Hi Michael,

On 11/9/18 4:45 AM, Michael Banck wrote:
>
> AIUI, this security issue only affects v10 and v11, but this is not
> clear from the announcement AFAICT, unless I missed it?
>
> I think it would be good to mention the exact versions that are affected
> by a CVE in the announcement; of course it is always possible to inspect
> the individual release notes, but having the information up front would
> be nice (again, unless I am missing something).

That is a fair point. I have looked through the past few announcements
and we have not included affected versions, just links to the CVE, which
do detail the versions available as well as the release notes which you
mention above. It probably would have helped to do that, and I look into
updating it on the website at a minimum.

That said, when I was drafting the announcement, it was becoming a bit
convoluted to craft clear instructions based on the security release +
additional upgrade steps for pg_stat_statements. I opted for keeping it
simple.

And there is still a problem of people not upgrading to the latest bug
fix releases. If there is language or motivation to continue to stay on
the point releases, personally I'd prefer to encourage that.

Thanks!

Jonathan


Attachment

pgsql-advocacy by date:

Previous
From: Michael Banck
Date:
Subject: Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released!
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25Released!