| From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 4321ip <4321ip(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15514: process fails on jsonb_populate_recordset query. see simple example below |
| Date: | 2018-11-22 23:23:37 |
| Message-ID: | CAJrrPGcVrGTnnCkB2wn+0KRLHNXAqNwbXwaVYOPzqW6gY2BBfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Nov 23, 2018 at 7:21 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> writes:
> > Accessing of NULL pointer leads to crash. Attached quick simple patch
> fixes
> > the problem.
>
> While that stops the crash, it doesn't do what we want, which is to
> return a valid tupdesc. Without that you get "set-valued function called
> in context that cannot accept a set" errors. I think the right fix is
> to force a call of update_cached_tupdesc so that there always is a
> tupdesc to copy.
>
Thanks for checking, I thought of the same thing, but I wasn't sure.
Regards,
Haribabu Kommi
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sandeep Thakkar | 2018-11-23 06:07:00 | Re: PostgreSQL v11 offline (portable) version libwinpthread-1.dll error |
| Previous Message | PG Bug reporting form | 2018-11-22 22:28:53 | BUG #15518: intarray index crashes hard |