Re: BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: samuel(dot)horwitz(at)gmail(dot)com
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered
Date: 2017-10-26 19:09:00
Message-ID: CA+q6zcVaseLjGTssxtr=yUkRY-sW8SKqPXsOpGsy10=u5UXWKA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 26 October 2017 at 20:40, <samuel(dot)horwitz(at)gmail(dot)com> wrote:
>
> However, if I alter the stored procedure's resulting JSON in any way, this
> will cause selecting from the second view to trigger a segfault.

Yes, looks like I can reproduce this issue - from the first glance
parse_relation.c:2216 is the culprit,
somehow aliasp_item is empty:

expandRTE (rte=<optimized out>, rtindex=3, sublevels_up=sublevels_up(at)entry=0,
location=-1, include_dropped=1 '\001', colnames=colnames(at)entry=0x7ffda83c0bd0,
colvars=0x7ffda83c0bd8) at parse_relation.c:2216
2216 char *label =
strVal(lfirst(aliasp_item));
>>> p aliasp_item
$1 = (ListCell *) 0x0

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2017-10-26 19:24:06 Re: BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered
Previous Message samuel.horwitz 2017-10-26 18:40:35 BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered