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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: samuel(dot)horwitz(at)gmail(dot)com, 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 20:42:36
Message-ID: 26672.1509050556@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> I haven't looked at this thing in details. But this data may not be
> present forever, say github.com is down or is removed from existence.
> So if you can, please always attach any self-contained test case in a
> way that it is saved in the archives of postgresql.org. In this case,
> that would have been to email directly pgsql-bugs instead of using the
> website form.

Thanks for posting the reproducer. The attached seems to fix it, but
now that I've seen this, I wonder if there are other similar cases.

regards, tom lane

Attachment Content-Type Size
make-expandRTE-cope-with-new-columns.patch text/x-diff 1.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-26 22:04:59 Re: BUG #14876: Segmentation fault with JSONB column used in store proc that gets used by view and later altered
Previous Message David G. Johnston 2017-10-26 20:23:03 Re: Segmentation fault with JSONB column from view passed into stored PL/PGSQL procedure that builds a new JSON return value