Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW]

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PATCH: make plpgsql IN args mutable (v1) [REVIEW]
Date: 2009-09-16 19:17:08
Message-ID: 4AB139B4.9060004@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael,

> This is also currently valid:
>
> CREATE FUNCTION mod (x int, y int)
> RETURNS int LANGUAGE plpgsql
> AS $f$
> DECLARE
> z INT := x % y;
> BEGIN
> RETURN z;
> END; $f$
>
> As is this:
>
> CREATE FUNCTION mod (x int, y int)
> RETURNS int LANGUAGE plpgsql
> AS $f$
> BEGIN
> RETURN (x % y);
> END; $f$

Certainly. I was doing that to have a simple example; obviously you
wouldn't write a mod funciton, and you wouldn't do it in plpgsql. There
are other case where the lack of mutability in IN parameters causes you
to create a throwaway variable.

--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tomas 2009-09-16 19:40:44 Re: WIP: generalized index constraints
Previous Message Josh Berkus 2009-09-16 19:16:37 Re: Feedback on getting rid of VACUUM FULL