| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Pavan Deolasee <pavan(dot)deolasee(at)2ndquadrant(dot)com> |
| Subject: | Re: rewrite HeapSatisfiesHOTAndKey |
| Date: | 2017-01-03 16:03:01 |
| Message-ID: | CA+Tgmoa7DqM09jTF6ts3bifdcEZ8oY-9vOQbtCSDPx_r5n5a5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 2, 2017 at 1:36 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Okay, but I think if we know how much is the additional cost in
> average and worst case, then we can take a better call.
Yeah. We shouldn't just rip out optimizations that are inconvenient
without doing some test of what the impact is on the cases where those
optimizations are likely to matter. I don't think it needs to be
anything incredibly laborious and if there's no discernable impact,
great. But it doesn't make sense to change things for the benefit of
WARM and indirect indexes and then discover later that we regressed
other cases we care about and have no plan to fix it. Better to find
out any potential problems of that kind now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2017-01-03 16:09:18 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |
| Previous Message | Robert Haas | 2017-01-03 15:59:11 | Re: Broken atomics code on PPC with FreeBSD 10.3 |