we will know whether this is a great thing we should continue, or we
should stick to our traditional laissez-faire style of project
management.  I figure that even if it really sucks, it wouldn't kill us
to try it for one release cycle --- at the very worst, we'd make up lost
time in future by no longer needing to waste bandwidth arguing about it.

Would this be a core postgresql code roadmap or something a bit
broader (contrib, custom types, GUI-ish stuff, utilities and what
have you)?

I think that we could at this time only expect things that would be submitted for core inclusion. The less cats to herd the better :)

Joshua D. Drake


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive 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

---------------------------(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

Reply via email to