| From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
|---|---|
| To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
| Cc: | pgsql-patches Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: plpgsql raise - parameters can be expressions |
| Date: | 2005-06-13 05:38:39 |
| Message-ID: | Pine.LNX.4.44.0506130737080.16737-100000@kix.fsv.cvut.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Mon, 13 Jun 2005, Michael Glaesemann wrote:
>
> On Jun 13, 2005, at 2:07 PM, Pavel Stehule wrote:
>
> > I did trivial patch which eliminate limit raise command. Using
> > expressions instead of variables are a little bit expensive, but
> > little.
>
> I'm right in thinking this essentially does the same thing as first
> assigning the value of the expression to a variable and then using
> the variable in the RAISE statement, correct? This patch just
> eliminates the step of assigning the value of the expression to the
> variable? If so, I'd expect the cost to be in line with the cost of
> explicitly assigning to a variable.
>
true, total cost is less
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2005-06-13 06:32:58 | Re: plpgsql raise - parameters can be expressions |
| Previous Message | Michael Glaesemann | 2005-06-13 05:23:35 | Re: plpgsql raise - parameters can be expressions |