Horton

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

Dmitry Dolgov <9erthalion6@gmail.com>

View thread View on postgr.es
From: Dmitry Dolgov <9erthalion6@gmail.com>
To: samuel.horwitz@gmail.com
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-10-26T19:09:00Z
Lists: pgsql-bugs 
> On 26 October 2017 at 20:40, <samuel.horwitz@gmail.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@entry=0,
location=-1, include_dropped=1 '\001', colnames=colnames@entry=0x7ffda83c0bd0,
colvars=0x7ffda83c0bd8) at parse_relation.c:2216
2216                                                    char       *label =
strVal(lfirst(aliasp_item));
>>> p aliasp_item
$1 = (ListCell *) 0x0

Commits

  1. Fix crash when columns have been added to the end of a view.