Re: Fix for gistchoose - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fix for gistchoose
Date
Msg-id CA+Tgmoai3fYgP_QcuVE3UrfAwXWsMQ5u1i8iiQYbyae7ut674A@mail.gmail.com
Whole thread Raw
In response to Re: Fix for gistchoose  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix for gistchoose
List pgsql-hackers
On Thu, Aug 30, 2012 at 1:27 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Mon, Aug 20, 2012 at 12:57 PM, Alexander Korotkov
>> <aekorotkov@gmail.com> wrote:
>>> I found that code of gistchoose doesn't follow it's logic. Idea of
>>> gistchoose is that first column penalty is more important than penalty of
>>> second column. If we meet same penalty values of first column then we choose
>>> minimal penalty value of second column among them.
>
>> Nice catch.  Thanks for the patch, which I have now committed.
>
> Should we backpatch that?

Arguably, yes.  Does the patch look sane to you?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: HEAD crashes on windows when doing VACUUM ANALYZE
Next
From: Robert Haas
Date:
Subject: Re: splitting *_desc routines