Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id KAA53552 for ; Sun, 18 Jul 1999 10:44:30 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA04366; Sun, 18 Jul 1999 10:43:21 -0400 (EDT) To: eem21@cam.ac.uk cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Asynchronous connect using libpq In-reply-to: Your message of Sun, 18 Jul 1999 11:51:26 +0100 (BST) Date: Sun, 18 Jul 1999 10:43:21 -0400 Message-ID: <4364.932309001@sss.pgh.pa.us> From: Tom Lane eem21@cam.ac.uk writes: > I need non-blocking versions of PQconnectdb and PQreset in libpq, > analogous to the asynchronous query processing functions (PQsendQuery > et al). Gonna have to write them yourself, I'm afraid. PQconnect is actually a rather long sequence, involving completing an authentication protocol with the server and then sending a few standard setup commands. See libpq/fe-connect.c. PQreset just closes the connection and then invokes PQconnect. > I am willing to write these, if no one else has time to do so, but would > appreciate some input before I get started. For maintainability, there'd need to be just one copy of the setup code not two, so you'd want to do something similar to the way I implemented the async query processing: write the async code and then replace the synchronous routines with simple loops that call the async version. Turning the bottom part of connectDB() plus PQsetenv() into a state machine would be a fairly straightforward way of making this happen. connectDB is nearly there already, you'd just need to move the loop up to its caller. Probably the most serious problem you'd have to consider before diving into this is that on most platforms, both gethostbyname() and connect() can involve nontrivial delays, and I know of no portable way to replace them with asynchronous operations. If you can live with a DNS lookup delay then you can probably live with the other delays, and if you can't then it's not clear you would have a workable solution when you got done anyway :-(. regards, tom lane