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

From Tom Lane
Subject Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column
Date
Msg-id 16591.1467056052@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
Peter Geoghegan <pg@heroku.com> writes:
> On Mon, Jun 27, 2016 at 8:21 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> A small-footprint answer that just occurred to me is to redefine the
>> threshold as being, not NBuffers, but maintenance_work_mem.  Then a
>> reasonably-sized test case could be made by reducing that to its minimum
>> allowed value.  This seems like it'd be fairly unsurprising for users
>> since there's lots of precedent for maintenance_work_mem affecting the
>> behavior of CREATE INDEX.

> I like this idea. Should I write a patch?

Please.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13907: Restore materialized view throw permission denied
Next
From: Tom Lane
Date:
Subject: Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column