Re: [HACKERS] Draft release notes for 9.4.4 et al
On 06/10/2015 11:35 PM, Noah Misch wrote: > On Tue, Jun 09, 2015 at 04:31:43PM -0700, Josh Berkus wrote: >> First draft of the release announcement. Noah, thank you for corrections! -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
On Tue, Jun 09, 2015 at 04:31:43PM -0700, Josh Berkus wrote: > First draft of the release announcement. > 2015-06-12 Update Release > = > > The PostgreSQL Global Development Group has released an update to all > supported versions of our database system, including 9.4.4, 9.3.9, 9.2.13, > 9.1.18 and 9.0.22. This release primarily fixes issues not successfully > fixed in prior releases. It should be applied as soon as possible by any user > who installed the May or June update releases. Other users should apply at > the next available downtime. The urgency is the same whether or not you installed the last couple of releases: ASAP if you're on 9.3 or 9.4, next-downtime otherwise. (A site on 9.4.1 doesn't have new problems, but the old problems were urgent enough.) > Crash Recovery Fixes > - > > Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 > with "multixact wraparound", but failed to account for issues doing multixact > cleanup during crash recovery. This could cause servers to be unable to > restart after a crash. As such, all users of 9.3 and 9.4 should apply this > update as soon as possible, expecially if they have already applied updates > 9.3.7, 9.3.8, 9.4.2 or 9.4.3. > > Database administrators who used pg_upgrade to upgrade to PostgreSQL version > 9.3 may find that applying the update causes an immediate autovacuum of their > entire database. Please see the [release > notes](http://www.postgresql.org/docs/9.4/static/release-9-3-9.html) for > details and ways to change the timing of the vacuum. This also affects sites that subsequently upgraded to 9.4. (Your text doesn't rule that out, but it bears mentioning explicitly.) Also, I suggest saying a bit more about the reasons for changing the timing of the vacuum. Consider this expansion of the second paragraph (but feel free to account for those considerations other ways instead): Clusters previously upgraded to PostgreSQL 9.3 using pg_upgrade, even those clusters now running PostgreSQL 9.4 due to another upgrade, may experience an immediate autovacuum of all tables after applying this update. For large clusters, consider a controlled manual VACUUM, before updating, to better regulate the performance consequences of this critical maintenance. See the release notes for details. > Cumulative Releases > --- > > All PostgreSQL update releases are cumulative. As this update release fixes > a number of problems inadvertently introduced by fixes in earlier update > releases, we strongly urge users to apply this update, rather than installing > less recent updates that have known issues. As this update release closes > all known bugs with multixact handling, the PostgreSQL Project does not > anticipate additional update releases soon. It does not close all known bugs with multixact handling; see point (2) here, for example: http://www.postgresql.org/message-id/20150608131504.gh24...@alap3.anarazel.de We nonetheless don't anticipate additional releases soon, but I would delete the last sentence. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
On 06/09/2015 05:17 PM, Michael Paquier wrote: > On Wed, Jun 10, 2015 at 8:41 AM, Josh Berkus wrote: >> On 06/09/2015 04:38 PM, Michael Paquier wrote: >>> On Wed, Jun 10, 2015 at 8:31 AM, Josh Berkus wrote: Tom, all: First draft of the release announcement. Please improve/edit/correct. Thanks! So, anyone else? Particularly, have I summed up the fixed multixact issue and how it affects 9.3 users correctly? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
On Wed, Jun 10, 2015 at 8:41 AM, Josh Berkus wrote: > On 06/09/2015 04:38 PM, Michael Paquier wrote: >> On Wed, Jun 10, 2015 at 8:31 AM, Josh Berkus wrote: >>> Tom, all: >>> >>> First draft of the release announcement. >>> >>> Please improve/edit/correct. Thanks! >> >> Some comments: >> s/expecially/especially. > > Thanks, fixed > >> >> This bug fix is not mentioned (worth it?): >> Avoid deadlock between incoming sessions and CREATE/DROP DATABASE > > Huh? Sorry. I'll blame the lack of sleep.. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
On 06/09/2015 04:38 PM, Michael Paquier wrote: > On Wed, Jun 10, 2015 at 8:31 AM, Josh Berkus wrote: >> Tom, all: >> >> First draft of the release announcement. >> >> Please improve/edit/correct. Thanks! > > Some comments: > s/expecially/especially. Thanks, fixed > > This bug fix is not mentioned (worth it?): > Avoid deadlock between incoming sessions and CREATE/DROP DATABASE Huh? * Avoid deadlock between new sessions and CREATE/DROP DATABASE > If not mentioned the fourth "*" is not needed in the list. Thanks, removed. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
On Wed, Jun 10, 2015 at 8:31 AM, Josh Berkus wrote: > Tom, all: > > First draft of the release announcement. > > Please improve/edit/correct. Thanks! Some comments: s/expecially/especially. This bug fix is not mentioned (worth it?): Avoid deadlock between incoming sessions and CREATE/DROP DATABASE If not mentioned the fourth "*" is not needed in the list. Regards, -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
Tom, all: First draft of the release announcement. Please improve/edit/correct. Thanks! -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com 2015-06-12 Update Release = The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.4.4, 9.3.9, 9.2.13, 9.1.18 and 9.0.22. This release primarily fixes issues not successfully fixed in prior releases. It should be applied as soon as possible by any user who installed the May or June update releases. Other users should apply at the next available downtime. Crash Recovery Fixes - Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 with "multixact wraparound", but failed to account for issues doing multixact cleanup during crash recovery. This could cause servers to be unable to restart after a crash. As such, all users of 9.3 and 9.4 should apply this update as soon as possible, expecially if they have already applied updates 9.3.7, 9.3.8, 9.4.2 or 9.4.3. Database administrators who used pg_upgrade to upgrade to PostgreSQL version 9.3 may find that applying the update causes an immediate autovacuum of their entire database. Please see the [release notes](http://www.postgresql.org/docs/9.4/static/release-9-3-9.html) for details and ways to change the timing of the vacuum. Other Fixes and Improvements In addition to the above, a few other minor issues were patched in this release. These fixes include: * Prevent failure to invalidate relation cache init file * Avoid deadlock between new sessions and CREATE/DROP DATABASE * Improve query planning for semi-joins and anti-joins * Cumulative Releases --- All PostgreSQL update releases are cumulative. As this update release fixes a number of problems inadvertently introduced by fixes in earlier update releases, we strongly urge users to apply this update, rather than installing less recent updates that have known issues. As this update release closes all known bugs with multixact handling, the PostgreSQL Project does not anticipate additional update releases soon. Updating As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Users who have skipped multiple update releases may need to perform additional post-update steps; see the Release Notes for details. See also the above note for users who used pg_upgrade with PostgreSQL version 9.3. Links: * [Download](http://www.postgresql.org/download) * [Release Notes](http://www.postgresql.org/docs/current/static/release.html) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
Andres Freund wrote: > Hi, > > On 2015-06-09 13:09:27 -0400, Tom Lane wrote: > > I've pushed up draft release notes for 9.4.4 at > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=21187cfc7dfd82461db9119377a76366c00d27c3 > > Please review and comment ASAP, particularly if the instructions regarding > > avoiding emergency autovacuuming are not accurate. > > Generally looks good. +1 > Some of the references to 9.3 in the 9.4 release notes don't seem > relevant though - I guess you intend to adjust them when "spreading" > the notes to all versions? Specifically "You must use > PostgreSQL 9.3.5 or later to perform this step." seems > likely to confuse users, given there's no corresponding 9.4 release. Oh, right, 9.4beta2 was released at the same time as 9.3.5, so by the time 9.4 was out, it already contained the fixes. -- Álvaro Herrerahttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
Andres Freund writes: > On 2015-06-09 13:09:27 -0400, Tom Lane wrote: >> I've pushed up draft release notes for 9.4.4 at >> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=21187cfc7dfd82461db9119377a76366c00d27c3 >> Please review and comment ASAP, particularly if the instructions regarding >> avoiding emergency autovacuuming are not accurate. > Generally looks good. Some of the references to 9.3 in the 9.4 release > notes don't seem relevant though - I guess you intend to adjust them > when "spreading" the notes to all versions? Specifically "You must use > PostgreSQL 9.3.5 or later to perform this step." seems > likely to confuse users, given there's no corresponding 9.4 release. Hm. It's valid for 9.4.x users, but I agree probably unnecessary. Will drop it in the 9.4.4 version. > I wonder if it'd be good to weaken "Users can avoid that by doing manual > vacuuming before upgrading to this release." a bit, further > emphasizing that that's optional. OK. Thanks for reviewing! regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Draft release notes for 9.4.4 et al
Hi, On 2015-06-09 13:09:27 -0400, Tom Lane wrote: > I've pushed up draft release notes for 9.4.4 at > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=21187cfc7dfd82461db9119377a76366c00d27c3 > Please review and comment ASAP, particularly if the instructions regarding > avoiding emergency autovacuuming are not accurate. Generally looks good. Some of the references to 9.3 in the 9.4 release notes don't seem relevant though - I guess you intend to adjust them when "spreading" the notes to all versions? Specifically "You must use PostgreSQL 9.3.5 or later to perform this step." seems likely to confuse users, given there's no corresponding 9.4 release. I wonder if it'd be good to weaken "Users can avoid that by doing manual vacuuming before upgrading to this release." a bit, further emphasizing that that's optional. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Draft release notes for 9.4.4 et al
I've pushed up draft release notes for 9.4.4 at http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=21187cfc7dfd82461db9119377a76366c00d27c3 Please review and comment ASAP, particularly if the instructions regarding avoiding emergency autovacuuming are not accurate. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
