The DBD::PgPP error now appears to be something else entirely (long story). I have posted the DBD::Pg question on the PostgreSQL DBD::Pg mailing list.
But if anyone happens to know the answer please don't hesitate to speak up! mma > -----Original Message----- > From: Marc M. Adkins [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 22, 2003 12:08 PM > To: [EMAIL PROTECTED] > Subject: PostgreSQL w/ithreads > > > Is anyone using PostgreSQL in a multi-threaded environment? > > With the native DBD::Pg 1.22 driver I get: > > [Fri Jun 20 11:47:57 2003] [error] [client 127.0.0.1] > DBD::Pg::dr default_user failed: handle 1 > is owned by thread 126e2e4 > not current thread 11df014 > (handles can't be shared between threads and > your driver may need a CLONE method added) > > The DBD::PgPP 0.04 driver doesn't give me the previous error, but just now > I've gotten: > > DBI->connect(dbname=user;host=localhost) failed: > FATAL 1: XLogFlush: request 0/12832B0 is not satisfied --- > flushed only to 0/12061CC > > which looks suspiciously like a multi-threading issue. > > Anyone know for certain that the Perl PostgreSQL drivers have or have not > been fixed for ithreads? > > Windows 2000, ActiveState 804 (5.8), mod_perl 1.99.10-dev. > > mma > >
