X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F1061D1B1C8 for ; Sun, 25 Jul 2004 07:51:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 28147-07 for ; Sun, 25 Jul 2004 10:51:43 +0000 (GMT) Received: from ms-smtp-03-eri0.socal.rr.com (ms-smtp-03-qfe0.socal.rr.com [66.75.162.135]) by svr1.postgresql.org (Postfix) with ESMTP id E03F9D1B18C for ; Sun, 25 Jul 2004 07:51:33 -0300 (ADT) Received: from [192.168.1.102] (24-25-208-96.san.rr.com [24.25.208.96]) by ms-smtp-03-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id i6PApaOD012570; Sun, 25 Jul 2004 03:51:37 -0700 (PDT) Subject: Re: 7.5 release notes From: Jeff Davis To: Bruce Momjian Cc: PostgreSQL-documentation In-Reply-To: <200407250425.i6P4PhI29389@candle.pha.pa.us> References: <200407250425.i6P4PhI29389@candle.pha.pa.us> Content-Type: text/plain Message-Id: <1090752696.1676.212.camel@jeff> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 25 Jul 2004 03:51:36 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/32 X-Sequence-Number: 2440 On Sat, 2004-07-24 at 21:25, Bruce Momjian wrote: > I have completed the 7.5 release notes. You can view them in HTML on > the developer web page. I have marked a few items with question marks > that need to be addressed. I am looking for improvements, even minor > ones. Either send in a patch or committers can modify the file > directly. I don't understand the following passage: "When matching GROUP BY names, prefer local FROM columns first, then SELECT aliases, and then outer FROM columns (Tom) This change was made because it is considered more consistent than the previous behavior." Perhaps it could be more clear? I don't know where else I'd go to find more thorough documentation on that subject. Also, I've included a couple typo fixes below. Regards, Jeff Davis --- release.html.old 2004-07-25 03:06:28.000000000 -0700 +++ release.html 2004-07-25 03:10:21.000000000 -0700 @@ -99,7 +99,6 @@

Before this change some queries would not use an index if the data types did not exactly match. This improvement makes index usage more intuitive and consistent. - match exactly

  • New buffer replacement strategy that improves caching (Jan)

    Prior releases use a least-recently-used (LRU) cache to keep recently referenced pages in the cache. Unfortunately, the cache @@ -129,7 +128,7 @@ resulting in improved performance. The close relationship between our developers and users reporting problems allows us to make rapid and complex optimizer improvements that would be very - difficult for lose-source companies to emulate. + difficult for closed-source companies to emulate.

  • Improve btree index performance for duplicate keys (Dmitry Tkach, Tom)

    This improves the way indexes are scanned when many duplicate values exist in the index.