ECPG connection timeouts

From: "Edmund Bacon" <edmund(dot)bacon(at)devstudios(dot)com>
To: <pgsql-interfaces(at)postgresql(dot)org>
Subject: ECPG connection timeouts
Date: 2008-03-18 22:47:51
Message-ID: ABAE5512DA3D4E4597C82947769214380138B9CB@devmail.devstudios.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Is it possible to control how long ECPG takes when trying to connect to
a database on a remote system (e.g. connect to tcp:postgres//remote/db)

In my environment it is quite possible that the link to the remote
system may be down, so I'd prefer not to have to force the end-user to
wait 3+ minutes while ECPG CONNECT times out.

I've tried using sig_action()/alarm() and also tried using
setjmp/longjmp with alarm, but to no avail.

Is there anything I can do within ECPG other than try a plain old
connect() to the remote system on port 5432 and not proceed with a ECPG
CONNECT if that fails?

Thanks,

Edmund Bacon

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Michael Meskes 2008-03-23 17:34:10 Re: ECPG connection timeouts
Previous Message Bruce Momjian 2008-03-07 17:54:05 Re: v8.1: Error severity on libpq PGconn*