> > OK, seems Vadim can turn this off easily, which is what I expected.
> > The big question is whether we want to stop working on the "features"
> > list to put out a release?
> No
Hmm. istm that several of the folks expecting to make major changes
for a 7.0 release are not able to work on it (much anyway) for the
next couple of months. Tom Lane is the only one to have feet in both
camps (big (?) changes already committed, more coming) but perhaps he
might reconsider his vote for "no 6.6". A 6.6 release cycle would get
that stuff out in the field and tested soon (Jan/Feb timeframe) rather
than waiting 'til May/June to start intensive testing.
I know that we made the commitment for v7.0 (and that waffling on that
issue for past releases drove me nuts ;), but I suspect that what we
already have in the code tree could come close to standing on its own
(especially in light of easily disabling the WAL framework, per
Vadim's note).
I could have "join syntax" ready for a 6.6 (no major changes to the
query tree required), then do the outer joins (with bigger query
tree/optimizer changes) and date/time reunification for 7.0...
- Thomas
Maybe we could steal Scott McNealy's (of Sun Microsystems) term for
Win2K for our 7.0 release:
"The big hairball"
:))
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California