| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Arrays of domains |
| Date: | 2017-09-29 13:22:09 |
| Message-ID: | e195a45f-06a7-310a-0a6b-760a771e2ce6@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/28/2017 05:44 PM, Tom Lane wrote:
>
> I get these query timings in a non-cassert build:
>
> HEAD Patch
>
> Q1 5453.235 ms 5440.876 ms
> Q2 9340.670 ms 10191.194 ms
> Q3 19078.457 ms 18967.279 ms
> Q4 48196.338 ms 58547.531 ms
>
>
[ analysis elided]
>
> Assuming that that's going to happen for v11, I'm inclined to leave the
> optimization problem until the dust settles around CaseTestExpr.
> Does anyone feel that this can't be committed before that's addressed?
>
>
I'm Ok with it as long as we don't forget to revisit this.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-09-29 13:25:09 | Re: Enhancements to passwordcheck |
| Previous Message | Alvaro Herrera | 2017-09-29 13:17:54 | Re: Enhancements to passwordcheck |