Re: [DOCS] 7.5 release notes
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.old2004-07-25 03:06:28.0 -0700 +++ release.html2004-07-25 03:10:21.0 -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. ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] 7.5 release notes
On Sun, Jul 25, 2004 at 00:25:43 -0400, Bruce Momjian <[EMAIL PROTECTED]> 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. There is a typo (transaction is misspelled) in the following line: Prior release had no such capability; there was no way to recover from a statement failure in a transation. This "match exactly" at the end of the following appears to be spurious: 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 In the following paragraph there appear to be two typos. I think "optimizer make" should be "optimizer makes" and that "lose-source" should be "closed-source". It is difficult to explain all the optimizer improvements that go into a release like this. They involve complex adjustments to the logic used to select indexes, join methods, and join order. They are difficult to explain, but the result is that the optimizer make quicker and better choices in how to execute queries, 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. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] 7.5 release notes
Jeff Davis <[EMAIL PROTECTED]> writes: > 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." That shouldn't be there at all, since the change was made and documented in 7.4.3. We don't normally duplicate previous release notes, do we? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] [DOCS] 7.5 release notes
Bruno Wolff III <[EMAIL PROTECTED]> writes: > In the following paragraph there appear to be two typos. I think > "optimizer make" should be "optimizer makes" and that "lose-source" > should be "closed-source". > It is difficult to explain all the optimizer improvements that go into a release > like this. They involve complex adjustments to the logic used to select indexes, > join methods, and join order. They are difficult to explain, but the result is that > the optimizer make quicker and better choices in how to execute queries, 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. I'd suggest removing the paragraph entirely, on the grounds that it is content-free fluff. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] 7.5 release notes
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. In E.1.1 Overview: "... This release supports Windows NT 4 and all later releases. It does not support earlier releases like Windows 95, 98, or ME because ... " Win98 and WinME is released _after_ NT4. See http://www.computerhope.com/history/windows.htm Perhaps it's better to say: "We only support NT-based Windows such as NT4, Win2k/XP/2003/later. Old 9x-based Windows versions such as Win95/98/Me are not supported because ..." Btw, can 7.5 run on WinCE/XP Media Center/XP SP2/etc? -- dave ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] Tutorial
Perhaps after OSCON I can work with fetter on getting the documentation clarified. OK? --elein On Fri, Jul 23, 2004 at 12:34:13PM -0700, David Fetter wrote: > On Fri, Jul 23, 2004 at 03:31:47PM -0400, Tom Lane wrote: > > David Fetter <[EMAIL PROTECTED]> writes: > > > What *is* broken is table inheritance, and the docs need to reflect > > > this. > > > > The combination of inheritance with certain other features is broken, > > yes, and the docs do reflect that (see the bottom of > > http://www.postgresql.org/docs/7.4/static/ddl-inherit.html > > for example). > > > > I will grant you that this page is a near duplicate of the > > tutorial's discussion of inheritance, which is surely bad --- either > > they should be exact duplicates, or one or the other needs > > rewriting. But I'm not really going to hold still for the docs on > > inheritance being rewritten by someone who considers the entire > > concept broken. Maybe we can get elein to do it ;-) > > I don't consider the concept broken. The implementation is, in fact, > broken, and putting that broken piece in the tutorial is, imnsho, a > bad mistake. > > Cheers, > D > -- > David Fetter [EMAIL PROTECTED] http://fetter.org/ > phone: +1 510 893 6100 mobile: +1 415 235 3778 > > Remember to vote! > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [DOCS] [HACKERS] Tutorial
Postgresql is not simply a relational database. It is an
OBJECT relational database. It was designed to be so from
the start. To pretend it was designed otherwise is to
deny its design and heritage and the original intent of
the the project. c.f. the postgres papers, stonebraker, et.al.
And like tom said, "who said inheritance is not relational."
It need not break codds rules.
--elein
On Thu, Jul 22, 2004 at 10:40:45PM -0400, Robert Treat wrote:
> On Thursday 22 July 2004 21:07, Joe Conway wrote:
> > elein wrote:
> > > I like inhertitance, but believe that the usefulness
> > > of our implementation is limited and so the documentation
> > > should focus on other areas.
> >
> > +1
> >
>
> +1/2 (Since I don't like inheritence)
>
> IMHO we ought to try to keep the _tutorial_ free of things that are generally
> considered against relational design. If we must keep them, move them into
> thier own section and lable them accordingly.
>
> Robert Treat
> ---
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
> ---(end of broadcast)---
> TIP 4: Don't 'kill -9' the postmaster
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] 7.5 release notes
Bruce Momjian said: > 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 presume we can also just make some comments ;-) this item: Add new GUC parameter to report useful information at the start of each log line should probably read "Add new GUC parameter log_line_prefix ." I think this item belongs to me, or me and Tom: Replace the virtual_host and tcpip_socket parameters with a unified listen_addresses parameter. Conversely, Tom deserves joint billing for dollar quoting, as most of what I did was based on his work. David Fetter should be mentioned under the dollar quoting and plperl items, as he did documentation for both. Tom's implementation of a new flex-based lexer for psql is a significant source code change which should be mentioned. cheers andrew ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] Tutorial
[EMAIL PROTECTED] (Tom Lane) writes:
> David Fetter <[EMAIL PROTECTED]> writes:
>> On Fri, Jul 23, 2004 at 04:30:40PM -0400, Tom Lane wrote:
>>> If we're going to remove from the tutorial every feature for which
>>> any aspect is deemed by someone to be broken, the tutorial is liable
>>> to become quite short.
>
>> Are there other pieces that are broken?
>
> Between the locale behavior and the trailing-spaces behavior, one could
> make the case that the entire set of textual datatypes are broken.
> Other examples will occur to your thought if you follow pgsql-bugs.
>
> My point here is that one man's unusably broken feature may be another
> man's quite useful feature. Postgres is a work in progress, and
> probably always will be. I don't object to pointing out shortcomings,
> but removing all mention of a feature because it has some shortcomings
> seems not the best way.
Ah, but suggesting that people devote time to adding documentation for
less controversial features, so that we actually _do_ see some more
documentation, seems a good thing :-).
--
output = reverse("moc.enworbbc" "@" "enworbbc")
http://cbbrowne.com/info/multiplexor.html
Why isn't phonetic spelled the way it sounds?
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] 7.5 release notes
On Sun, 2004-07-25 at 05: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. > Looks good. These take time and effort, much appreciated. Forward-looking phrases === Overall, I'd ask that we don't refer back to what earlier releases didn't do, or whatever limitations they were thought to have. If a release has "new feature X", everybody can work out it wasn't there in the last release. The phrasing is delicate so you describe the new thing without running down the old. e.g. (1) Previous releases required the Unix emulation toolkit Cygwin for Win32 support. to The server no longer relies upon Cygwin for Unix emulation under win32. e.g. (2) Prior release had no such capability; there was no way to recover from a statement failure in a transaction. to Should a statement fail inside a transaction, there is now a way to handle this error and continue processing. (Of course, somebody will let me know about my Brit-style passive voice, I'm sure...) Migration = These release notes refer to "GUC"s, whereas the previous release notes and the manual refers to "server configuration parameters". I understand the former, but prefer the latter description for these user-focused notes. Also, it might be worth mentioning that pg_dump itself has also been substantially improved, and now provides an improved upgrade path for existing users. Here's my attempt at a short paragraph for PITR... Point-In-Time Recovery enhances Data Resilience PostgreSQL can now recover from total disk failure using backups and transaction log archives. Recovery can be controlled to stop at a specified point in time or at some transaction in the past. Transaction log archiving is automated and calls a user-supplied external program to allow integration with external backup devices and related software. > Do people want a big-picture paragraph at the top talking about the > release? Some releases get them, some don't, but this one could if > folks want it. > Yes, thats a good idea. Best Regards, Simon Riggs ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] [HACKERS] 7.5 release notes
Simon Riggs wrote: > On Sun, 2004-07-25 at 05: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. > > > > Looks good. These take time and effort, much appreciated. > > Forward-looking phrases > === > > Overall, I'd ask that we don't refer back to what earlier releases > didn't do, or whatever limitations they were thought to have. > > If a release has "new feature X", everybody can work out it wasn't there > in the last release. The phrasing is delicate so you describe the new > thing without running down the old. > > e.g. (1) > > Previous releases required the Unix emulation toolkit Cygwin for Win32 > support. > > to > > The server no longer relies upon Cygwin for Unix emulation under win32. > > e.g. (2) > > Prior release had no such capability; there was no way to recover from a > statement failure in a transaction. > > to > > Should a statement fail inside a transaction, there is now a way to > handle this error and continue processing. > > (Of course, somebody will let me know about my Brit-style passive voice, > I'm sure...) I understand your reason for making these changes. However, I am unsure if your new wording is as clear as the previous one. Our reliance on Cygwin and inability to prevent an error from aborting a transaction were limitation and it seems clearer to just state that we have fixed them rather than try to sugar-code our previous limitations. Marketing-wise, I think you are right, but from an honesty/clarity perspective, I think the current wording is better. What I could do is remove some of the later references where we were talking updating the system catalog to do various things. I am not sure it is needed. Comments? > > Migration > = > These release notes refer to "GUC"s, whereas the previous release notes > and the manual refers to "server configuration parameters". I understand > the former, but prefer the latter description for these user-focused > notes. Updated. > Also, it might be worth mentioning that pg_dump itself has also been > substantially improved, and now provides an improved upgrade path for > existing users. It is mentioned as the top item in the pg_dump section. It doesn't seem like a migration issue to me though. Is it a major feature? > Here's my attempt at a short paragraph for PITR... > > Point-In-Time Recovery enhances Data Resilience > > PostgreSQL can now recover from total disk failure using backups and > transaction log archives. Recovery can be controlled to stop at a > specified point in time or at some transaction in the past. Transaction > log archiving is automated and calls a user-supplied external program to > allow integration with external backup devices and related software. We can improve the wording, but if the motivation is to reduced saying bad things about our previous functionality, let me explain my perspective. Basically, my goal with these release notes is to make it as clear as possible why this new feature would be valuable to the reader. If it makes our previous release look bad, so be it. For me, clarity and candor gain a lot more credibility than trying to cover over missing functionality in the past. I am not saying we have to be so honest that we bash PostgreSQL, but in cases where we adjust wording to try to prevent ourselves from looking bad, it is best to be honest and clear about our limitations. I think in the long run it gains us lots of credibility (and ultimately volunteers). > > > Do people want a big-picture paragraph at the top talking about the > > release? Some releases get them, some don't, but this one could if > > folks want it. > > > > Yes, thats a good idea. OK. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [DOCS] 7.5 release notes
Tom Lane wrote: > Jeff Davis <[EMAIL PROTECTED]> writes: > > 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." > > That shouldn't be there at all, since the change was made and documented > in 7.4.3. We don't normally duplicate previous release notes, do we? Agreed. Removed. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [DOCS] 7.5 release notes
Jeff Davis wrote: > 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. Item removed. Tom said it was already in 7.4.3. I made the adjustments below. --- > > Also, I've included a couple typo fixes below. > > Regards, > Jeff Davis > > --- release.html.old2004-07-25 03:06:28.0 -0700 > +++ release.html2004-07-25 03:10:21.0 -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. > > > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [DOCS] [HACKERS] 7.5 release notes
All added. Thanks. --- Andrew Dunstan wrote: > Bruce Momjian said: > > 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 presume we can also just make some comments ;-) > > this item: > > Add new GUC parameter to report useful information at the start of each > log line > should probably read "Add new GUC parameter log_line_prefix ." > > I think this item belongs to me, or me and Tom: > > Replace the virtual_host and tcpip_socket parameters with a unified > listen_addresses parameter. > > Conversely, Tom deserves joint billing for dollar quoting, as most of what I > did was based on his work. > > David Fetter should be mentioned under the dollar quoting and plperl items, > as he did documentation for both. > > Tom's implementation of a new flex-based lexer for psql is a significant > source code change which should be mentioned. > > cheers > > andrew > > > > > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [DOCS] 7.5 release notes
Bruno Wolff III wrote: > On Sun, Jul 25, 2004 at 00:25:43 -0400, > Bruce Momjian <[EMAIL PROTECTED]> 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. > > There is a typo (transaction is misspelled) in the following line: > Prior release had no such capability; there was no way to recover from a statement > failure in a transation. This > > "match exactly" at the end of the following appears to be spurious: Yes, removed. > 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 > > In the following paragraph there appear to be two typos. I think > "optimizer make" should be "optimizer makes" and that "lose-source" > should be "closed-source". > It is difficult to explain all the optimizer improvements that go into a release > like this. They involve complex adjustments to the logic used to select indexes, > join methods, and join order. They are difficult to explain, but the result is that > the optimizer make quicker and better choices in how to execute queries, 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. Fixed.> -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] [DOCS] 7.5 release notes
\Tom Lane wrote: > Bruno Wolff III <[EMAIL PROTECTED]> writes: > > In the following paragraph there appear to be two typos. I think > > "optimizer make" should be "optimizer makes" and that "lose-source" > > should be "closed-source". > > > It is difficult to explain all the optimizer improvements that go into a release > > like this. They involve complex adjustments to the logic used to select indexes, > > join methods, and join order. They are difficult to explain, but the result is > > that the optimizer make quicker and better choices in how to execute queries, > > 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. > > I'd suggest removing the paragraph entirely, on the grounds that it is > content-free fluff. Hey, that's your content-free fluff. :-) You make major optimizer improvements in every release, but they are so complex it is impossible to explain them to people. This paragraph tries to address that. However, since you don't like it, I will remove it entirely. If you change your mind we can re-add it. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [DOCS] [HACKERS] 7.5 release notes
Adjustment made: http://pgfoundry.org/projects/pginstaller. This release supports NT-based Windows releases like NT4, Win2k, XP, Win2003. Older releases like Windows 95, 98, and ME are not supported because these operating systems do not have the infrastructure to support PostgreSQL. --- David Garamond wrote: > 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. > > In E.1.1 Overview: "... This release supports Windows NT 4 and all later > releases. It does not support earlier releases like Windows 95, 98, or > ME because ... " > > Win98 and WinME is released _after_ NT4. See > > http://www.computerhope.com/history/windows.htm > > Perhaps it's better to say: "We only support NT-based Windows such as > NT4, Win2k/XP/2003/later. Old 9x-based Windows versions such as > Win95/98/Me are not supported because ..." > > Btw, can 7.5 run on WinCE/XP Media Center/XP SP2/etc? > > -- > dave > > ---(end of broadcast)--- > TIP 8: explain analyze is your friend > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] [DOCS] 7.5 release notes
All fixed. Thanks. --- Bruno Wolff III wrote: > On Sun, Jul 25, 2004 at 00:25:43 -0400, > Bruce Momjian <[EMAIL PROTECTED]> 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. > > There is a typo (transaction is misspelled) in the following line: > Prior release had no such capability; there was no way to recover from a statement > failure in a transation. This > > "match exactly" at the end of the following appears to be spurious: > > 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 > > In the following paragraph there appear to be two typos. I think > "optimizer make" should be "optimizer makes" and that "lose-source" > should be "closed-source". > It is difficult to explain all the optimizer improvements that go into a release > like this. They involve complex adjustments to the logic used to select indexes, > join methods, and join order. They are difficult to explain, but the result is that > the optimizer make quicker and better choices in how to execute queries, 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. > > ---(end of broadcast)--- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] 7.5 release notes
On Mon, 2004-07-26 at 00:55, Bruce Momjian wrote: > Simon Riggs wrote: > > On Sun, 2004-07-25 at 05: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. > > > > > > > Those were just examples of a suggested style change for some items. > Basically, my goal with these release notes is to make it as clear as > possible why this new feature would be valuable to the reader. Completely Agree. > If it makes our previous release look bad, so be it. Oh. > For me, clarity and > candor gain a lot more credibility than trying to cover over missing > functionality in the past. I am not saying we have to be so honest that > we bash PostgreSQL, but in cases where we adjust wording to try to > prevent ourselves from looking bad, it is best to be honest and clear > about our limitations. I think in the long run it gains us lots of > credibility (and ultimately volunteers). > I see this as merely a half-full/half-empty viewpoint issue. Honesty and clarity are wonderful things and I subscribe to them. Using them only to describe your own viewpoint is not a reasonable point to make in a hopefully rational discussion about writing style... I'll go back to my docs now, but I guess we may relive this again when you see some of the honest, clear and positive changes I am suggesting. :) -- Best Regards, Simon Riggs ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [DOCS] [HACKERS] 7.5 release notes
Simon Riggs wrote: > > For me, clarity and > > candor gain a lot more credibility than trying to cover over missing > > functionality in the past. I am not saying we have to be so honest that > > we bash PostgreSQL, but in cases where we adjust wording to try to > > prevent ourselves from looking bad, it is best to be honest and clear > > about our limitations. I think in the long run it gains us lots of > > credibility (and ultimately volunteers). > > > > I see this as merely a half-full/half-empty viewpoint issue. > > Honesty and clarity are wonderful things and I subscribe to them. Using > them only to describe your own viewpoint is not a reasonable point to > make in a hopefully rational discussion about writing style... > > I'll go back to my docs now, but I guess we may relive this again when > you see some of the honest, clear and positive changes I am suggesting. > :) I wasn't suggesting yours were dishonest. I was saying that I was aiming for the clearest style whether is makes PostgreSQL look good or not. I figured saying "in the past you had to do X" was clearer than saying "you don't have to do X anymore". I am, of course, am open to the community's feedback on this. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
