Re: BUG #14134: segmentation fault with large table with gist index

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: yjh0502(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14134: segmentation fault with large table with gist index
Date: 2016-05-11 16:47:50
Message-ID: 57336236.3060200@timbira.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11-05-2016 12:49, yjh0502(at)gmail(dot)com wrote:
> The postgresql server crashed with segfault. Here's an index which causes
> the crash:
>
It seems someone (5ea86e6e?) forgot to assign CurrentMemoryContext to
ssup_ctx. I am not sure if it should be done at
PrepareSortSupportFromOrderingOp or elsewhere.

--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2016-05-11 18:41:40 Re: BUG #14132: ON CONFLICT not inferring unique index with bigints
Previous Message yjh0502 2016-05-11 15:49:04 BUG #14134: segmentation fault with large table with gist index