| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Transform for pl/perl |
| Date: | 2018-04-11 14:38:20 |
| Message-ID: | 6600cf29-dec6-f9fc-d6d8-388736aa64d8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/10/18 07:33, Dagfinn Ilmari Mannsåker wrote:
> 1) both the jsonb_plperl and jsonb_plperlu extensions contain the SQL
> functions jsonb_to_plperl and plperl_to_jsonb, so can't be installed
> simultaneously
>
> 2) jsonb scalar values are passed to the plperl function wrapped in not
> one, but _two_ layers of references
>
> 3) jsonb numeric values are passed as perl's NV (floating point) type,
> losing precision if they're integers that would fit in an IV or UV.
>
> 4) SV_to_JsonbValue() throws an error for infinite NVs, but not NaNs
>
> Attached is a patch for the first issue. I'll look at fixing the rest
> later this week.
Committed #1. Please keep more patches coming. :)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Corbet | 2018-04-11 14:40:31 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Andres Freund | 2018-04-11 14:29:09 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |