Re: RFD: Don't force plpgsql IN parameters to constant - Mailing list pgsql-hackers

From Tom Lane
Subject Re: RFD: Don't force plpgsql IN parameters to constant
Date
Msg-id 26834.1248916315@sss.pgh.pa.us
Whole thread Raw
In response to Re: RFD: Don't force plpgsql IN parameters to constant  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> First reaction is that it would mean we could never pass them by 
> reference. I know PLPerl uses in effect pass by copy, but what does 
> PLPgsql do?

It's not really an issue, because plpgsql keeps track of whether
the current value of the variable "belongs" to it or not.  Look
at the "freeval" manipulations in pl_exec.c.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Next
From: Robert Haas
Date:
Subject: Re: RFD: Don't force plpgsql IN parameters to constant