Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Daniel Newman <dtnewman(at)gmail(dot)com>, danielnewman(at)umich(dot)edu, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Date: 2016-06-25 15:32:19
Message-ID: 32645.1466868739@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Fri, Jun 24, 2016 at 3:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, it won't run automatically --- unless someone spins up a buildfarm
>> machine that adds that symbol to CPPFLAGS, and even then we'd only have
>> coverage on one platform.

> I think that this is an argument against further proliferation of
> #define's for this kind of thing, not an argument against adding a way
> to force tuplesort based hash index builds.

So ... what's your point? This statement doesn't seem to lead to a
conclusion in favor of either of the alternatives I mentioned.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Francisco Olarte 2016-06-25 16:13:34 Re: Database Creation
Previous Message Mr Mashele Comfort 2016-06-25 14:46:46 Database Creation