Re: plpgsql raise - parameters can be expressions

Поиск
Список
Период
Сортировка
От Michael Glaesemann
Тема Re: plpgsql raise - parameters can be expressions
Дата
Msg-id B705B9DF-80F4-4534-B9BA-B9C3A7B19737@myrealbox.com
обсуждение исходный текст
Ответ на plpgsql raise - parameters can be expressions  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
Ответы Re: plpgsql raise - parameters can be expressions  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
Список 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

В списке pgsql-patches по дате отправления:

Предыдущее
От: Christopher Kings-Lynne
Дата:
Сообщение: Re: plpgsql raise - parameters can be expressions
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: plpgsql raise - parameters can be expressions