X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 424A4474E44 for ; Wed, 12 Feb 2003 23:31:52 -0500 (EST) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id D6E5E474E42 for ; Wed, 12 Feb 2003 23:31:51 -0500 (EST) Received: by news.hub.org (Postfix, from userid 8) id C2D5E43A666; Wed, 12 Feb 2003 23:31:51 -0500 (EST) From: "Frankie Lam" X-Newsgroups: comp.databases.postgresql.sql Subject: Re: dblink question please Date: Thu, 13 Feb 2003 12:32:54 +0800 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 33 Message-ID: References: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 To: pgsql-sql@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/274 X-Sequence-Number: 11672 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" 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. > >