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: 2009-07-30 01:06:41
Message-ID: 45A52E17-DE6E-4A07-A5AA-CCEA501218E5@cisco.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-30 01:08:47 Re: RFD: Don't force plpgsql IN parameters to constant
Previous Message Steve Prentice 2009-07-30 01:05:17 Re: RFD: Don't force plpgsql IN parameters to constant