Yah!
That's exactly what I did already(did this to all lines containing
`elog(ERROR...)'. :-D
But, I'm still experiencing some error messages when I'm doing 'extreme'
test to
plpgsql functions,
for example 'ExecMakerTableFunctionResult: Invalid result from function
returning tuple'.
I really have no idea about what this message is related to the dblink
functions. Any idea
about it? Thanks so much.
Regards, Frankie.
"Frankie Lam" <frankie@ucr.com.hk> wrote in message
news:b2etmt$26en$1@news.hub.org...
> Hello,
>
> Does anyone know if there's a simple way that let dblink function calls in
a
> plpgsql function wouldn't raise exception, in case there's sth wrong.
> (e.g. cannot connect to the remote host ......)
>
> I want this because I want to have more controls over plpgsql function, as
> plpgsql only offers a very limited error exception handler.
>
> Regards, Frankie.
>
>
