Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C70622E0090 for ; Tue, 18 Mar 2008 19:54:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 76928-06 for ; Tue, 18 Mar 2008 19:54:21 -0300 (ADT) X-Greylist: delayed 00:12:09.563148 by SQLgrey-1.7.5 Received: from devstudios.com (ip-216-194-85-181.tera-byte.com [216.194.85.181]) by postgresql.org (Postfix) with ESMTP id 88C3E2E0060 for ; Tue, 18 Mar 2008 19:54:27 -0300 (ADT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: ECPG connection timeouts X-MIMEOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 18 Mar 2008 16:47:51 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ECPG connection timeouts Thread-Index: AciJSU/IqElOx92aSQuppUS+TVFrbQ== From: "Edmund Bacon" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.1 tagged_above=0 required=5 tests=RDNS_DYNAMIC=0.1 X-Spam-Level: X-Archive-Number: 200803/2 X-Sequence-Number: 6709 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.=20 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