Re: Planning to force reindex of hash indexes

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "Mendola Gaetano" <mendola(at)bigfoot(dot)com> writes:
>> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I've found a number of infelicities in the hash index code that
>>> can't be fixed without an on-disk format change.
>
>> How can we avoid this kind of mess for the future ?
>
> Build a time machine, go back fifteen years, wave a magic wand to
> increase the IQ levels of the Berkeley grad students? Sometimes we
> just have to change bad decisions, that's all.
>
> regards, tom lane

Actually, I think that your time would be better spent on the time
machine. After all, with working time travel you wouldn't have to
worry about optimizing PostgreSQL. Queries could take as long as they
needed to take and then you could send the response back in time to
right before the query was issued.

It's too bad you don't have the time machine finished already. You
could use the time machine to go back in time and work on the time
machine :). You'd be finished in no time.

Jason