Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org
	(8.8.8/8.7.5) with ESMTP id LAA22356 for
	<pgsql-interfaces@postgreSQL.org>;
	Sun, 9 Aug 1998 11:33:32 -0400 (EDT)
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 LAA04097;
	Sun, 9 Aug 1998 11:33:24 -0400 (EDT)
To: Goran Thyni <goran@bildbasen.se>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg 
In-reply-to: Your message of Sun, 09 Aug 1998 08:16:36 +0000
	<35CD5AE4.DE2DF2B8@bildbasen.se>
Date: Sun, 09 Aug 1998 11:33:24 -0400
Message-ID: <4095.902676804@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Goran Thyni <goran@bildbasen.se> writes:
> DBD::Pg dos indeed use PQconnectdb(),
> but at least in my light test I get SEGV in $sth->fetch.
> The problems are probably somewhere in DBDI or DBD::Pg or
> somewhere in the interaction of the parts.

FWIW, I finally got around to installing Perl5 (5.004 pl4 to
be specific), and so far the perl5 interface supplied with pgsql
seems to work fine.  I only just now realized that what you
are talking about is something different ... the code included
in the distribution calls itself Pg not DBD::Pg.  What versions
of everything are you using?

> I am looking into how much work a "pure Perl" interface
> should amount to. Using native perl IO and pgsql-fe/be-protocol
> should make "pgsql-clienting" even more portable over platforms.

Of course, it will also mean that you have to maintain that code
every time we change the fe/be protocol ... there is a change
upcoming for 6.4.

			regards, tom lane