| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Caleb Welton <cwelton(at)greenplum(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] plpythonu datatype conversion improvements |
| Date: | 2009-08-17 15:04:02 |
| Message-ID: | 4A897162.5020807@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>
> For the record, I think this entire patch is a bad idea. PLs should not
> be so much in bed with the internal representation of datatypes.
>
I thought there was some suggestion in the past that we should move some
in that direction. The discussion context was Theo Schlossnagle's
complaint about the overhead of passing bytea to and from PLPerl,
although that might be ameliorated by the hex gadget. The other major
case that would benefit would be passing Array values as the PL's native
array type, and Composite values as the PL's associative array type.
That would save PL users a lot of highly error-prone coding
deconstructing the text representation of such objects.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Olszak | 2009-08-17 15:11:22 | Pl/perlu, DBD::Oracle and Sys:SigAction problem - crash of backend process |
| Previous Message | Tom Lane | 2009-08-17 14:42:49 | Re: [PATCH] plpythonu datatype conversion improvements |