My feeling is that we ought to bounce bitmap indexes and updatable views
as not being ready, accept all the contrib stuff, and try to get the
other items done in time for a beta at, say, the end of next week.
I'm not thrilled about postponing those two large items till 8.3, but
we are a month past feature freeze and we do not have credible patches
in hand for either.
I know there is a lot of "backend" work that has been done for 8.2 but
the two features you are suggesting we bounce, are probably the most
visible of marketable features we will have for this release. Especially
updateable views.
The alternative is to be willing to slip the
schedule until whenever they are ready, and we have learned the hard way
that that's not good project management.
Well I don't like the idea either, but if it isn't done, it isn't done.
How often do we hear the complaint about software that is shipped before
it is done?
Outside of feature freeze, we really haven't had AFAICS a "solid"
release schedule. Is it going to be push Beta for a month? Does that
push us till the end of the year?
I don't know which is the better solution, but you asked for comments :)
Sincerely,
Joshua D. Drake
Comments?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
