On Thu, 14 Sep 2006, Joshua D. Drake wrote:
Well on that same vein (with a +1), I know that we lost at least 8 weeks
of productivity from various vacations etc.. during the summer. When you
incorporate everyone else that is involved with postgresql, I could
easily see almost a full man year lost, by having freeze where it is
now.
I think having a freeze more toward march/april makes a heck of a lot of
sense.
Not against the idea ... would push more for March freeze though ... that
way admins can plan for upgrades over their 'slow summer months' ... March
would effectively look at a June 1st (-ish) release, so even a bit of a
slip would still see it as the summer starts ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
---------------------------(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
