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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 02:57:09
Message-ID: 3685.1248922629@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Hmm, well if I understand this correctly (now), it's similar to allowing:

> void
> test2(int a)
> {
> a = 2;
> return;
> }

> ...which is a fairly common programming practice that I don't think is
> particularly considered bad style, or at least certainly not by
> everyone.

Right, you could only change the local copy of the parameter value.
It's certainly not demonstrably horrible ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-07-30 03:05:48 machine-readable explain output v4
Previous Message Steve Prentice 2009-07-30 02:43:02 Re: RFD: Don't force plpgsql IN parameters to constant