Re: plpgsql raise - parameters can be expressions

From: Neil Conway <neilc(at)samurai(dot)com>
To: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: plpgsql raise - parameters can be expressions
Date: 2005-06-13 12:01:04
Message-ID: 42AD7580.1000901@samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Pavel Stehule wrote:
> I did trivial patch which eliminate limit raise command.

In thinking about this some more, it would be nice to be able to use
exec_eval_expr() to reduce expression evaluation overhead for simple
RAISE parameters. It is easy enough to refactor the current
exec_eval_expr() code so this is possible, but it will be of only
limited use: PL/PgSQL currently only considers expressions that result
in a single attribute as sufficiently simple that they can be evaluated
via ExecEvalExpr(). I wonder how much work it would take to lift this
restriction...

-Neil

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Atsushi Ogawa 2005-06-13 13:15:14 EUC_JP and SJIS conversion improvement
Previous Message Pavel Stehule 2005-06-13 07:16:28 Re: plpgsql raise - parameters can be expressions