| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | yjh0502(at)gmail(dot)com, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14134: segmentation fault with large table with gist index |
| Date: | 2016-05-11 19:37:48 |
| Message-ID: | CAM3SWZTrnui1h0yJW+idbSxQFpOU5yrHjrpr0D-aELs5==tM9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 11, 2016 at 9:47 AM, Euler Taveira <euler(at)timbira(dot)com(dot)br> wrote:
> 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.
That commit did not change anything about memory contexts, and did not
add new functionality to the SortSupport path taken here.
The bug is in commit 35fcb1b3, which failed to initialize ssup_ctx.
I'm surprised that it took this long for there to be trouble, because
that commit doesn't initialize anything at all in the sortsupport
object.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-05-11 19:56:38 | Re: BUG #14134: segmentation fault with large table with gist index |
| Previous Message | Peter Geoghegan | 2016-05-11 18:41:40 | Re: BUG #14132: ON CONFLICT not inferring unique index with bigints |