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 19:01:17 |
Message-ID: | 19501.1466881277@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 Sat, Jun 25, 2016 at 8:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So ... what's your point? This statement doesn't seem to lead to a
>> conclusion in favor of either of the alternatives I mentioned.
> I'm in favor of just adding a debug option. We should introduce a more
> general idea of a #define that enables a variety of debugging options,
> because it's silly to have to worry about buildfarm coverage each and
> every time this crops up. I'm not entirely sure what level that should
> be scoped at. The status quo is impractical.
I don't exactly see how that leads to any improvement --- you still end
up having to manually configure some buildfarm critters for coverage, no?
> Incidentally, did you see to it that there is buildfarm coverage for
> RAW_EXPRESSION_COVERAGE_TEST?
Yes, see dromedary.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-06-25 19:05:47 | Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column |
Previous Message | Peter Geoghegan | 2016-06-25 18:52:47 | Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column |