| From: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Amit Langote <amitlangote09(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] path toward faster partition pruning |
| Date: | 2018-05-07 07:30:12 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07-05-2018 4:37, Michael Paquier wrote:
> On Fri, May 04, 2018 at 12:32:23PM +0300, Marina Polyakova wrote:
>> I got a similar server crash as in [1] on the master branch since the
>> commit
>> 9fdb675fc5d2de825414e05939727de8b120ae81 when the assertion fails
>> because
>> the second argument ScalarArrayOpExpr is not a Const or an ArrayExpr,
>> but is
>> an ArrayCoerceExpr (see [2]):
>
> Indeed, I can see the crash. I have been playing with this stuff and I
> am in the middle of writing the patch, but let's track this properly
> for
> now.
Thank you very much!
--
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-05-07 07:56:22 | Re: [HACKERS] path toward faster partition pruning |
| Previous Message | Sergei Kornilov | 2018-05-07 07:29:26 | Re: Having query cache in core |