X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9B78B47628A for ; Thu, 13 Feb 2003 00:28:43 -0500 (EST) Received: from joeconway.com (unknown [63.210.180.150]) by postgresql.org (Postfix) with ESMTP id 70ED5475F84 for ; Thu, 13 Feb 2003 00:24:31 -0500 (EST) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.4) with ESMTP-TLS id 1610220; Wed, 12 Feb 2003 21:59:37 -0800 Message-ID: <3E4B2BA5.3020409@joeconway.com> Date: Wed, 12 Feb 2003 21:22:45 -0800 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frankie Lam Cc: pgsql-sql@postgresql.org Subject: Re: dblink question please References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/276 X-Sequence-Number: 11674 Frankie Lam wrote: > 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. Sounds like you didn't heed my warning. It is *probably* safe to make the elog(ERROR...) to elog(NOTICE...) change *in that one function*, dblink_connect(), and then use persistent connections, e.g. select dblink_connect('dbname=blah ...'); select * from dblink('select f1 from foo') as (f1 text); If instead you made the change within the dblink_record() function, and you weren't careful to add additional error handling, then the message you got is what I'd expect. You basically broke dblink for those scenarios. Joe