Re: plpgsql raise - parameters can be expressions

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
Cc: pgsql-patches Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: plpgsql raise - parameters can be expressions
Date: 2005-06-13 05:23:35
Message-ID: B705B9DF-80F4-4534-B9BA-B9C3A7B19737@myrealbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


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.

Definitely nifty!

Michael Glaesemann
grzm myrealbox com

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Pavel Stehule 2005-06-13 05:38:39 Re: plpgsql raise - parameters can be expressions
Previous Message Christopher Kings-Lynne 2005-06-13 05:13:22 Re: plpgsql raise - parameters can be expressions