| From: | Steve Prentice <prentice(at)cisco(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PATCH: make plpgsql IN args mutable (v1) |
| Date: | 2009-09-21 04:01:36 |
| Message-ID: | AD33A76E-B369-4FC5-BE61-1E8D347383AC@cisco.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thank you!
-Steve
On Sep 19, 2009, at 6:55 PM, Tom Lane wrote:
Steve Prentice <prentice(at)cisco(dot)com> writes:
> This patch changes plpgsql IN parameters so they are mutable.
I've applied this, since the consensus seemed to be in favor of it.
> I decided not to update the docs for this change because the docs
> don't currently indicate that an IN parameter is constant and I didn't
> want to encourage it because it isn't universally considered good
> programming practice to assign to an IN parameter. If others think we
> need a doc change for this, I'll update the patch.
I agree, no need to say anything one way or the other in the plpgsql
docs.
We'll want to mention it in the release notes of course.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-09-21 04:21:43 | Re: TODO item: Allow more complex user/database default GUC settings |
| Previous Message | Josh Williams | 2009-09-21 04:00:29 | Re: Encoding issues in console and eventlog on win32 |