From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Server crashed with dense_rank on partition table. |
Date: | 2018-06-13 07:29:42 |
Message-ID: | CAKJS1f8FahHKk3mw4mEHUVrSbinTUtbF7No+pfKteyn6UdP0sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 June 2018 at 17:55, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Jun 13, 2018 at 11:08:38AM +0530, Rajkumar Raghuwanshi wrote:
>> postgres=# SELECT dense_rank(b) WITHIN GROUP (ORDER BY a) FROM pagg_tab
>> GROUP BY b ORDER BY 1;
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> The connection to the server was lost. Attempting reset: Failed.
>
> Indeed, thanks for the test case. This used to work in v10 but this is
> failing with v11 so I am adding an open item. The plans of the pre-10
> query and the query on HEAD are rather similar, and the memory context
> at execution time looks messed up.
Looks like some memory is being stomped on somewhere.
4b9094eb6 (Adapt to LLVM 7+ Orc API changes.) appears to be the first
bad commit.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-06-13 07:35:58 | Re: Server crashed with dense_rank on partition table. |
Previous Message | Peter Geoghegan | 2018-06-13 06:32:43 | Re: Duplicate Item Pointers in Gin index |