Hello,
I know I will probably be flamed into oblivion for this but I would
like to make a suggestion about
the upcoming release.
What if we delayed until the end of the year?
The two reasons that I can come up with are:
1. The irritating (but work around capable) bigint index issue. 2. More importantly the recent potential discovery
byJan on vacuum.
I have several high end users that are really beating their heads
against the wall with even lazy vacuum
because of how brutal it can be on the system. If we could make vacuum a
little less harsh it could be
a large boon.
If I am totally off my rocker, so be it but if we were to hit the
streets with 7.4 and a vacuum that was 70% (ex)
less brutal on the machine it would be a pretty significant statement.
Yes all the other fixes are great and cool.
Sincerely,
Joshua D. Drake
Tom Lane wrote:
>Barring the discovery of any major new bugs, the core committee has
>agreed to release 7.4RC1 on Monday. Time to get those last-minute
>fixes in place.
>
>I currently have the following issues on my radar screen:
>
>Force GRANT/REVOKE by superuser to act as though owner of object?
>Change libpgtcl to use ByteArray for lo_read/lo_write (ljb's patch)
>Add option for parallelism limit in make check (Andrew Dunstan's patch)
>rule/foreign key interaction reported by Michele Bendazzoli
>
>plus various minor documentation fixes. Not much there...
>
>BTW, 7.4 final will be as early as the following Monday if no problems
>are detected. We will decide on a week-to-week basis whether we are
>ready to release final or not.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org