Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VFXrE08878 for ; Thu, 31 May 2001 11:33:53 -0400 (EDT) (envelope-from jtv@xs4all.nl) Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id RAA18079; Thu, 31 May 2001 17:33:48 +0200 (CEST) Received: (from jtv@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) id RAA00245; Thu, 31 May 2001 17:33:48 +0200 (CEST) Date: Thu, 31 May 2001 17:33:47 +0200 From: jtv To: pgsql-interfaces@commandprompt.com Cc: pgsql-interfaces@postgresql.org Subject: Re: libpq++ in Apache Problem. Message-ID: <20010531173347.C29317@xs4all.nl> Mail-Followup-To: pgsql-interfaces@commandprompt.com, pgsql-interfaces@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from pgsql-interfaces@commandprompt.com on Tue, May 29, 2001 at 07:42:46AM -0700 X-Archive-Number: 200105/130 X-Sequence-Number: 1660 On Tue, May 29, 2001 at 07:42:46AM -0700, pgsql-interfaces@commandprompt.com wrote: > > The next step in trouble-shooting this I suppose is to build the dummy > Apache module with libpq++ and see if it the same behavior is exhibited. > If not, it's got to be something deeper in the core of my module. Have you tried using just libpq, and just "inlining" the code that libpq++ *should* be executing based on your invocations? Sounds like you don't even need the PQresult structure to reproduce the problem, so it should be doable. Jeroen