Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group