Jerry Sievers wrote:
> Bricklen Anderson <[EMAIL PROTECTED]> writes:
>
>
>>I couldn't find any useful references in the docs or archives for emitting the
>>line number of a plpgsql function (in a RAISE statement). I'd like to use it
>>for
>>debugging some complex functions.
>>Does anyone have any tips on where to look, or an example of this?
>
>
> Have a look at the m4 macro processor
>
> changequote({,})dnl
> define({func_body},{$$begin
> raise exception 'I barfed on line #__line__';
> end$$})dnl
>
> create function some_func()
> returns whatever
> as func_body
> language plpgsql;
>
> This can be useful sometimes... but may ADD to your debugging
> headaches if not used artfully!
>
> HTH
>
I'll look into that, thanks for the suggestion.
Cheers,
Bricklen
--
_______________________________
This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use or
copying of this e-mail or the information it contains by other than an
intended recipient is unauthorized. If you received this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.
_______________________________
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
