Re: Composite Types and Function Parameters - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Composite Types and Function Parameters
Date
Msg-id 4CC62FAA.7090505@dunslane.net
Whole thread Raw
In response to Re: Composite Types and Function Parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Composite Types and Function Parameters  (Andrew Dunstan <adunstan@postgresql.org>)
Re: Composite Types and Function Parameters  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers

On 10/25/2010 07:12 PM, Tom Lane wrote:
> However, that objection doesn't hold for plperl or pltcl (and likely
> not plpython, though I don't know that language enough to be sure).
> So it would be a reasonable feature request to teach those PLs to
> accept "record" parameters.  I think the fact that they don't stems
> mostly from nobody having revisited their design since the
> infrastructure that supports record_out was created.

That seems like a good idea. I'll look at it for plperl.

cheers

andrew


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: xlog.c: WALInsertLock vs. WALWriteLock
Next
From: Robert Haas
Date:
Subject: Re: security hook on authorization