| 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-27 19:34:12 |
| Message-ID: | 16591.1467056052@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 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?
Please.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-27 20:22:25 | Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column |
| Previous Message | pbaugher | 2016-06-27 19:15:35 | BUG #14216: pgadmin 4, beta 2, no data displays |