Re: 7.5 release notes
От | Jeff Davis |
---|---|
Тема | Re: 7.5 release notes |
Дата | |
Msg-id | 1090752696.1676.212.camel@jeff обсуждение исходный текст |
Ответ на | 7.5 release notes (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: 7.5 release notes
Re: 7.5 release notes |
Список | pgsql-docs |
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 @@ </p><p> 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 </p></li><li><p> New buffer replacement strategy that improves caching (Jan) </p><p> 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. </p></li><li><p> Improve btree index performance for duplicate keys (Dmitry Tkach, Tom) </p><p> This improves the way indexes are scanned when many duplicate values exist in the index.
В списке pgsql-docs по дате отправления: