| 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-24 21:56:54 |
| Message-ID: | CAM3SWZTyfbs2YQ0OMWMW0MZMfSKAkPKtusdhTKS+3FLdL9kEww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jun 24, 2016 at 2:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I agree that we need to do something, but I'm not very clear on what
> the something is. I considered inventing a debug #define that would
> reduce the _h_spool threshold to the minimum workable amount (2, looks
> like), but I'm not sure how much that will help. What did you have
> in mind?
I think we should do that. Why do you say that you're not sure how
much it will help?
It may have escaped your attention, so I'll point out that amcheck
regression tests are my solution to testing external sorting, an area
which is similarly sorely lacking.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-24 22:05:45 | Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column |
| Previous Message | Tom Lane | 2016-06-24 21:20:45 | Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column |