Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA38281 for ; Thu, 6 Jan 2000 13:41:07 -0500 (EST) (envelope-from lamar.owen@wgcr.org) Received: from wgcr.org ([206.74.232.197]) by www.wgcr.org (8.9.3/8.9.3/WGCR) with ESMTP id NAA09287; Thu, 6 Jan 2000 13:41:08 -0500 Message-ID: <3874E1BD.D7440BBB@wgcr.org> Date: Thu, 06 Jan 2000 13:41:01 -0500 From: Lamar Owen Organization: WGCR Internet Radio X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker CC: pgsql-interfaces@postgresql.org, vev@hub.org, Alexander Barkov Subject: Re: [INTERFACES] Re: Adding a Search Link ... (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The Hermit Hacker wrote: > > Erk...I know *someone* was working on this...did we ever get anywhere on a > thread-safe libpq? Well, I don't think it has been fully documented, but the current libpq, as long as you don't use one connect method, and use another -- apparently PQsetdbLogin IS threadsafe, as the AOLserver driver uses that successfully. I THINK (I would search the archives, but.... Don Baccus posted a question about just that at one point, and it was answered) PQconnectdb is not, but don't quote me on that. The short of it is that AOLserver, a multithreaded webserver, successfully uses PQsetdbLogin -- which is apparently thread-safe. Once the connection is established, libpq is apparently thread-safe. (at least it is operating under a multithreaded webserver....) -- Lamar Owen WGCR Internet radio 1 Peter 4:11