This isn't something that is going to serve the person who loose all the sleep to configure and maintain it. It is something that is going to help the PostgreSQL community has a whole, to grow in a reasonably organized and hopefully less painful way.
Maybe I didn't express myself properly. I didn't mean that Brendan should do all the work by himself -- but expecting the whole community, or the usual developers, to do the initial effort, is not likely to make this plane fly. Because the current developers are already comfortable with the current state of affairs, why should they worry about changing the process? This is something the rest of the people can do, for their own sake. It can, of course, serve the community eventually.
O.k. then I misunderstood and apologize. I think the above is reasonable. I wouldn't think that the main developers would stop developing to create this system, nor would I want them to take time away from development to implement it.
I would however think that the main developer buy off would be essential. If the primary memebers of the development community said o.k. we are going to implement foo... who wants to spear head it? That would be a good thing.
Would you expect Bruce to enter each and every TODO item in a bug tracking system?
Well that depends... if it replaced the current TODO list as the definitive source then yes I would.
I wouldn't. Would I register my own "pet peeves" in
such a system? Probably I would.
Sincerely,
Joshua D. Drake
-- Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240 PostgreSQL Replication, Consulting, Custom Programming, 24x7 support Managed Services, Shared and Dedication Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
