Alvaro Herrera <alvhe...@commandprompt.com> writes:
> Excerpts from Bruce Momjian's message of vie oct 14 11:56:22 -0300 2011:
>> Tom Lane wrote:
>>> There is plenty of stuff in the TODO list for which there is no
>>> consensus.
>> Uh, we should probably remove those then. Can you think of any?
> Unless something is blatantly "not wanted", I don't think it should be
> removed from the TODO list. There not being consensus does not mean
> that there cannot ever be.
Yeah. The reason why something is on the TODO list (and not already
done) is typically one of
1. It's too hard, or too long/boring for the expected value.
2. There's no consensus about how to implement the feature.
3. There's no consensus about the user-visible design of the feature.
Cases where there's debate about whether we want it at all seem to me
to be a subset of #3. But for anything in #3, someone could do the
legwork or have the bright idea needed to create consensus about how
to design the feature.
My gripe about the TODO list is not that we have some stuff in there
that's not clearly wanted, it's that some of the entries fail to make
it clear where the issue stands on this scale. That could lead people
to waste time trying to code something that there's not consensus for
the design or implementation of.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
