Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Wed, 29 Jul 2009 21:11:55 -0400
- Message-id: <26834.1248916315@sss.pgh.pa.us> <text/plain>
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
- References:
- RFD: Don't force plpgsql IN parameters to constant
- From: Steve Prentice
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Andrew Dunstan
- RFD: Don't force plpgsql IN parameters to constant
- Prev by Date: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by Date: Re: RFD: Don't force plpgsql IN parameters to constant
- Previous by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Indexes: