pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Frankie Lam <frankie@ucr.com.hk>
Cc: pgsql-sql@postgresql.org
Subject: Re: dblink question please
Date: Thu, 13 Feb 2003 04:30:59 -0800
Message-ID: <3E4B9003.6060907@joeconway.com> (raw)
In-Reply-To: <b2fh7r$1nph$1@news.hub.org>
References: <b2etmt$26en$1@news.hub.org>
	<b2fh7r$1nph$1@news.hub.org>

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




view thread (8+ messages)  latest in thread

Message-ID: <3E4B9003.6060907@joeconway.com>
Permalink:  ../3E4B9003.6060907@joeconway.com/
Also on:    postgresql.org/message-id/3E4B9003.6060907@joeconway.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: mail@joeconway.com, frankie@ucr.com.hk
  Subject: Re: dblink question please
  In-Reply-To: <3E4B9003.6060907@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox