Re: plpgsql raise - parameters can be expressions

Поиск
Список
Период
Сортировка
От Neil Conway
Тема Re: plpgsql raise - parameters can be expressions
Дата
Msg-id 42AE60BA.4040208@samurai.com
обсуждение исходный текст
Ответ на Re: plpgsql raise - parameters can be expressions  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: plpgsql raise - parameters can be expressions  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-patches
Tom Lane wrote:
> But you had mentioned wanting to look at reducing overhead by using
> exec_eval_expr(); were you intending to do that before committing?

I'm a bit busy with other matters at the moment, so I'll probably look
at it later. One question is whether we should make use of
exec_eval_expr() by representing the RAISE parameter list as a list of
expressions (each of which would likely be simple enough to evaluate via
ExecEvalExpr()), or whether we want to extend exec_eval_expr() to handle
  expressions that yield multiple attributes.

-Neil

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

Предыдущее
От: Neil Conway
Дата:
Сообщение: hash join: probe both inputs first
Следующее
От: Tom Lane
Дата:
Сообщение: Re: plpgsql raise - parameters can be expressions