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: Steve Prentice <prentice(at)cisco(dot)com>
- To: Andrew Dunstan <andrew(at)dunslane(dot)net>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: RFD: Don't force plpgsql IN parameters to constant
- Date: Wed, 29 Jul 2009 18:06:41 -0700
- Message-id: <45A52E17-DE6E-4A07-A5AA-CCEA501218E5@cisco.com> <text/plain>
On Jul 29, 2009, at 5:23 PM, Andrew Dunstan wrote:
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?
Isn't this effectively what we accomplish with an IN/OUT parameter?
- 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: