Re: Server crashed with dense_rank on partition table.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Server crashed with dense_rank on partition table.
Date: 2018-06-13 05:55:34
Message-ID: 20180613055534.GB26669@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2018-06-13 06:01:46 Re: Duplicate Item Pointers in Gin index
Previous Message Rajkumar Raghuwanshi 2018-06-13 05:38:38 Server crashed with dense_rank on partition table.