X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E3494474E4F for ; Thu, 13 Feb 2003 07:32:58 -0500 (EST) Received: from joeconway.com (unknown [63.210.180.150]) by postgresql.org (Postfix) with ESMTP id 484C6474E42 for ; Thu, 13 Feb 2003 07:32:58 -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 1610469; Thu, 13 Feb 2003 05:07:52 -0800 Message-ID: <3E4B9003.6060907@joeconway.com> Date: Thu, 13 Feb 2003 04:30:59 -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/286 X-Sequence-Number: 11684 Frankie Lam wrote: > Now I use only persistent connection inside my PLPGSQL functions, the > EXCEPTION "ExecMakerTableFunctionResult: Invalid result from function > returning tuple" has gone. Good. > It seems to me this is a matter of libPQ (because connect_timeout > doesn't work in the case), but someone told me this is nothing to do > with libPQ, and it's possible a matter of KERNEL and transport layer > of tcp protocol.(I don't really understand these stuff) Is this > true?(If this is true, then I have to abort my project :-( ) > I'm afraid the person who gave you that answer knows much better than I. Perhaps there is some kernel tcp parameter you can adjust? Or maybe dblink just isn't an appropriate solution given your requirements. You haven't described what exactly you are trying to do, and what exactly are your requirements, so it's a bit hard to help there. Joe