Re: [pgsql-advocacy] [HACKERS] First draft of update announcement
On 03/19/2014 02:16 PM, Darren Duncan wrote: On 2014-03-18, 2:42 PM, Josh Berkus wrote: Other PostgreSQL 9.3 only fixes in this update include: * Add read-only data_checksum parameter I recall being told last fall that this would not be added to 9.3.x (9.3.1 at the time I think) and only to 9.4.x because such a feature addition was something only allowed for major releases and not minor ones which were just supposed to be security and bug fixes. So what changed that it is added in 9.3.x after all? Enough people reported operational problems with not having the parameter. -- 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] First draft of update announcement
On 03/18/2014 03:02 PM, Tom Lane wrote: Josh Berkus j...@agliodbs.com writes: Updated per feedback. CC'd to Advocacy now for additional corrections. A few thoughts: Changes incorporated. -- 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: [pgsql-advocacy] [HACKERS] First draft of update announcement
On 2014-03-18, 2:42 PM, Josh Berkus wrote: Other PostgreSQL 9.3 only fixes in this update include: * Add read-only data_checksum parameter I recall being told last fall that this would not be added to 9.3.x (9.3.1 at the time I think) and only to 9.4.x because such a feature addition was something only allowed for major releases and not minor ones which were just supposed to be security and bug fixes. So what changed that it is added in 9.3.x after all? -- Darren Duncan -- 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] First draft of update announcement
All, Updated per feedback. CC'd to Advocacy now for additional corrections. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.4, 9.2.8, 9.1.13, 9.0.19, and 8.4.20. This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes rows to vanish from indexes during recovery due to timing issues with updating locks. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to take a new base backup of each of their standby databases after applying the update. Other PostgreSQL 9.3 only fixes in this update include: * Make sure that statistics files for dropped databases get deleted * Allow materialized views to be referenced in UPDATE and DELETE queries * Add read-only data_checksum parameter * Prevent erroneous operator push-down in postgres_fdw This release resolves some other issues in all versions of PostgreSQL, including: * Fix timing consistency issue with NOTIFY * Allow regular expression execution to be cancelled * Remove ability to execute OVERLAPs with a single argument * Improve performance of index checks for newly added rows * Prevent premature walsender disconnection * Prevent memory errors on newer Windows versions * Update timezone files Additional changes and details of some of the above issues can be found in the Release Notes. Two of the issues which affect version 9.3 have additional information on the 9.3.4 Update Wiki Page. Users of version 8.4 should note that it will reach End-of-Life (EOL) three months from now, per our [Versioning Policy](http://www.postgresql.org/support/versioning/). This means that this is likely to be the next-to-last update for version 8.4, and users should be planning to upgrade to a newer version of PostgreSQL. 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. Links: * [Download](http://postgresql.org/download) * [Release Notes](http://www.postgresql.org/docs/current/static/release.html) * [9.3.4 Update Wiki Page](https://wiki.postgresql.org/wiki/20140320UpdateIssues) -- 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] First draft of update announcement
Josh Berkus j...@agliodbs.com writes: Updated per feedback. CC'd to Advocacy now for additional corrections. A few thoughts: The PostgreSQL Global Development Group has released an update to all supported version of the database system, including versions 9.3.4, 9.2.8, 9.1.13, 9.0.19, and 8.4.20. By my count, 9.0.17 and 8.4.21 are the correct minor numbers. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes rows to vanish from indexes during recovery due to timing issues with updating locks. Per earlier discussion, I think vanish from indexes is a bad choice of wording here: it will make people think they can recover by REINDEXing, which is not the case. I haven't got a great alternative wording though; best I can do offhand is causes table rows to become unreachable by index scans, which lacks punch. Also, although this isn't too important to users, the problem isn't a timing issue. How about ... during recovery due to incorrect replay of tuple locking operations, or some such? For this reason, users are encouraged to take a new base backup of each of their standby databases after applying the update. new base backup for, perhaps? With of, this sounds like you're telling people to make backups from the (corrupted) slave servers. * Remove ability to execute OVERLAPs with a single argument There wasn't ever any actual ability to execute such calls; there was only some code that tried to support the case and failed miserably. I'm not sure this is worth mentioning in the announcement, really --- but if you do, this is a poor description because it sounds like we removed a usable feature. 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
[HACKERS] First draft of update announcement
... attached. Please correct! -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com The PostgreSQL Global Development Group has released a critical update to version 9.3 of the database system. This minor release, PostgreSQL 9.3.4, fixes a data corruption issue with replication and crash recovery, as well as several other minor issues. All users of version 9.3 are urged to update their installations at the next opportunity. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes rows to vanish from indexes during recovery due to simultaneous updates of rows on both sides of a foreign key. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to take a new base backup of each of their standy databases after applying the update. This release resolves some other issues which affect PostgreSQL 9.3, including: * Make sure that statistics files for dropped databases get deleted * Fix timing consistency issue with NOTIFY * Allow materialized views to be referenced in UPDATE and DELETE queries * Allow regular expression execution to be cancelled * Remove ability to execute OVERLAPs with a single argument * Improve performance of index checks for newly added rows * Prevent premature walsender disconnection * Add read-only data_checksum parameter * Prevent memory errors on newer Windows versions * Prevent erroneous operator push-down in pgsql_fdw * Update timezone files Additional changes and details of some of the above issues can be found in the Release Notes. 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. Links: * [Download](http://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] First draft of update announcement
2014-03-17 13:24 GMT+09:00 Josh Berkus j...@agliodbs.com: ... attached. Please correct! A couple of drive-by corrections: each of their standy databases standy - standby Prevent erroneous operator push-down in pgsql_fdw pgsql_fdw - postgres_fdw Regards Ian Barwick -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
