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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-27 18:18:52
Message-ID: CAM3SWZTzzQmQU=a=XWiFEQyidXnSeRYEJOWf_YxWzRT04B=A-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 27, 2016 at 8:21 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-06-27 18:35:47 Re: BUG #13907: Restore materialized view throw permission denied
Previous Message Peter Geoghegan 2016-06-27 18:06:01 Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column