Justin Clift <justin@postgresql.org> writes:
> Tom Lane wrote:
>> This particular hole has been in *every* release since Postgres 1.01.
> How many releases have we known about this and still done a major
> release?
Several; a quick glance in the archives shows this has been on the TODO
list since 7.0.something.
I really have zero patience for arguments that "problem FOO is so bad
that we should drop everything else until we've fixed it". There are
too many possible candidates for problem FOO, and there are still only
24 hours in the day.
regards, tom lane
