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

From Peter Geoghegan
Subject Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Date
Msg-id CAM3SWZQqU8awdp6Q2_MHwCZC15qau23FTp19qka4NG+6U+fqjA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
List pgsql-bugs
On Fri, Jun 24, 2016 at 3:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think we should do that. Why do you say that you're not sure how
>> much it will help?
>
> 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.


--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #14195: "MultiXactId XXXXXX has not been created yet -- apparent wraparound" after upgrade from 9.2