From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | gregk(at)stoddarts(dot)com(dot)au |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15578: Executing json_populate_recordset with an empty array causes a segmentation fault |
Date: | 2019-01-07 05:12:28 |
Message-ID: | 13027.1546837948@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> When executing json_populate_recordset/jsonb_populate_recordset with an
> empty array, a segmentation fault occurs and the server process is
> terminated. The issue occurs regardless of the type used. In previous
> versions this would return null.
> Example:
> CREATE TYPE test_type AS (amount numeric, description text);
> SELECT * FROM json_populate_recordset(null::test_type,'[]');
Hm, this example works for me in HEAD and 11 branch tip, so I'm
guessing it was fixed by this commit:
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=595220a3a
That'll be out in 11.2, or you can apply the patch locally if
you're in a hurry.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bartosz Polnik | 2019-01-07 09:17:47 | Re: BUG #15577: Query returns different results when executed multiple times |
Previous Message | Michael Paquier | 2019-01-07 04:59:18 | Re: BUG #15578: Executing json_populate_recordset with an empty array causes a segmentation fault |