Re: RFD: Don't force plpgsql IN parameters to constant

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Steve Prentice <prentice(at)cisco(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Date: 2009-07-30 01:11:55
Message-ID: 26834.1248916315@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-07-30 02:32:25 Re: RFD: Don't force plpgsql IN parameters to constant
Previous Message Tom Lane 2009-07-30 01:08:47 Re: RFD: Don't force plpgsql IN parameters to constant