Re: [ANNOUNCE] PostgreSQL v7.1 Release Candidate 4 - Mailing list pgsql-hackers
From | Tatsuo Ishii |
---|---|
Subject | Re: [ANNOUNCE] PostgreSQL v7.1 Release Candidate 4 |
Date | |
Msg-id | 20010409102110R.t-ishii@sra.co.jp Whole thread Raw |
In response to | PostgreSQL v7.1 Release Candidate 4 (The Hermit Hacker <scrappy@hub.org>) |
List | pgsql-hackers |
Where can I get a Postscript version docs for 7.1? -- Tatsuo Ishii > Ladies and Gentlemen ... > > Its been a long, arduous, up hill battle to get to this point, with all of > the changes since v7.0 was released, but we're finally there ... > > > The PostgreSQL Global Development Group is *pleased* to announce the > availability of PostgreSQL v7.1 Release Candidate 4, the long awaited > successor to v7.0. > > > Before anyone asks what a 'Release Candidate' is, and what happened to > 1-3 ... a Release Candidate is what the developers have decided is going > to be the Release, based on no known bugs remaining, but want to get more > general testing. > > If, by Friday, April 13th, there have been no bugs reported, all that will > happen is that rc4 will get renamed as the official release, no > repackaging or anything ... > > What happened to 1-3? We packaged 1, one of the developers came across a > bug before an announcement went out, so we didn't announce ... similar to > the other 2. > > Please NOTE that this is *not* the official release ... this is what we > believe, at this time, is going to be the official release, based on > extensive testing over the past several months, but if someone reports a > bug based on this, it will be addressed and a new package built ... > > What does v7.1 provide that v7.0 didn't? From our HISTORY file: > > ================ > Major changes in this release: > > Write-ahead Log (WAL) - To maintain database consistency in case > of an operating system crash, previous releases of PostgreSQL have forced > all data modifications to disk before each transaction commit. With WAL, > only one log file must be flushed to disk, greatly improving performance. > If you have been using -F in previous releases to disable disk flushes, > you may want to consider discontinuing its use. > > TOAST - Previous releases had a compiled-in row length limit, > typically 8 - 32 kB. This limit made storage of long text fields > difficult. With TOAST, long rows of any length can be stored with good > performance. > > Outer Joins - We now support outer joins. The UNION/NOT IN > workaround for outer joins is no longer required. We use the SQL92 outer > join syntax. > > Function Manager - The previous C function manager did not handle > NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function > manager does. You can continue using your old custom functions, but you > may want to rewrite them in the future to use the new function manager > call interface. > > Complex Queries - A large number of complex queries that were > unsupported in previous releases now work. Many combinations of views, > aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now > work properly. Inherited tables are now accessed by default. Subqueries > in FROM are now supported. > ================= > > For a more complete list of New Features and Bugs Fixed, please read the > HISTORY segment available at: > > ftp://ftp.postgresql.org/pub/README.v7_1 > > Source code is available at ftp://ftp.postgresql.org/pub/v7.1 ... > > Please report any bugs that you encounter to pgsql-bugs@postgresql.org > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html >
pgsql-hackers by date: