Re: New News Entry - Mailing list pgsql-www
From | Devrim GUNDUZ |
---|---|
Subject | Re: New News Entry |
Date | |
Msg-id | Pine.LNX.4.44.0408232056440.7256-100000@emo.org.tr Whole thread Raw |
In response to | New News Entry (www@www.postgresql.com (World Wide Web Owner)) |
List | pgsql-www |
Hi, Thanks, approved. Regards, Devrim On Mon, 23 Aug 2004, World Wide Web Owner wrote: > A new entry has been added to the news database. > > Database Admin: http://www.postgresql.org/admin/edit_news.php?219 > > Submitted by: press@postgresql.org > Headline: Update Releases 7.2.5, 7.3.7, 7.4.5 Available, Recommended. > Summary: > > The PGDG has released patch versions for the last 3 versions of PostgreSQL. As the patches affect database recovery,upgrading is strongly recommended. (more ...) > > Story: > > Over the past week, we have bundled and released new versions of 7.2, 7.3 and 7.4 to address a couple of potentially criticalbugs that were recently identified. > > For all three versions, these releases address the following: > > * Prevent possible loss of committed transactions during crash. > Due to insufficient interlocking between transaction commit and checkpointing, it was possible for transactions committedjust before the most recent checkpoint to be lost, in whole or in part, following a database crash and restart. > > Specific to 7.4, the following has also been fixed: > > * Repair possible crash during concurrent btree index insertions > This patch fixes a rare case in which concurrent insertions into a btree index could result in a server panic.No permanent damage would result, but it\'s still worth a re-release. The bug does not exist in pre-7.4 releases. > > Due to the seriousness of the first bug, as relates to data integrity, it is strongly recommended that administrators upgradetheir database servers at their earliest convience. > > None of these releases require a dump-n-reload in order to address the problems. > > It should be noted that, for those looking to upgrade from a 7.4.0/7.4.1 server to 7.4.5, that there a dump-n-reload is*recommended* (but not required) to address a fix introduced between 7.4.1 and 7.4.2. Please refer to the 7.4.5 HISTORYfile for information on how this can be accomplished without a dump-n-reload, as there are steps that can be followedfor this. > > Please download <a href =\"http://www.postgresql.org/mirror-ftp.html\"> from one of our mirror sites</a>, or <a href=\"http://bt.postgresql.org\">from Bittorrent.</a> > > As always, please report any bugs to pgsql-bugs@postgresql.org > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > -- Devrim GUNDUZ devrim~gunduz.org devrim.gunduz~linux.org.tr http://www.tdmsoft.com http://www.gunduz.org