| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Adam Brusselback *EXTERN*'" <adambrusselback(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: No index only scan on md5 index |
| Date: | 2015-11-26 08:20:19 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B50FEB3D6@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Adam Brusselback wrote:
> I appreciate the response Tom, and you are correct that the workaround would not work in my case.
>
> So no index expressions can return the their value without recomputing without that work around? I
> learn something new every day it seems.
> Thank you for the alternate method.
No, what Tom said is that the check whether an "index only scan" was feasible
or not does not consider expressions.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glyn Astill | 2015-11-26 16:11:41 | Index scan cost calculation |
| Previous Message | Adam Brusselback | 2015-11-26 01:16:40 | Re: No index only scan on md5 index |