Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 03B1C9FB818 for ; Wed, 6 Jun 2007 00:51:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 84423-06 for ; Wed, 6 Jun 2007 00:51:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id EDD509FB83E for ; Wed, 6 Jun 2007 00:51:39 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l563pV628487; Tue, 5 Jun 2007 23:51:31 -0400 (EDT) From: Bruce Momjian Message-Id: <200706060351.l563pV628487@momjian.us> Subject: Re: about threaded libpq In-Reply-To: <200706051606.04810.mcousin@sigma.fr> To: Marc Cousin Date: Tue, 5 Jun 2007 23:51:31 -0400 (EDT) CC: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/33 X-Sequence-Number: 25701 Marc Cousin wrote: > Hi, > > I'm currently working with bacula developpers in order to improve performance > (mainly for postgresql). > > In order for our new code to work, we need to be sure that libpq is threaded. > For 8.2, we can use PQisthreadsafe();. The problem is we cannot force all > users to migrate to 8.2, and that many of them use packaged postgresql > binaries. > > Is there another reliable way to determine (at bacula configure time for > instance) that libpq is threaded ? (it also has to be a way/several ways that > works on all platforms, as bacula runs on many unix and win32). We'd like to > do it as well as possible. Uh, you can look at the 'pg_config --configure' output. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +