Message-Id: <200104081700.f38H09849242@postgresql.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
From: "Jeff Duffy" <jeff@alanne.com>
To: pgsql-interfaces@postgresql.org
Cc: "Lane, Tom" <tgl@greatbridge.com>, "Momjian,
 Bruce" <bruce@greatbridge.com>
Subject: Status of DBD:Pg and Pg interfaces for Perl
Date: 08 Apr 2001 12:00:11 EDT
Reply-To: "Jeff Duffy" <jeff@alanne.com>

Greetings.

  The RC3 release has an ancient version of the perl Pg interface in
/src/interfaces/Perl5, which predates the DBI architecture, the
de-facto standard for interfacing with a database from Perl. The
upshot of this is that most people will install the DBD::Pg module
from CPAN rather than use the older Pg interface in the source tree,
and neither Pg.pm or DBD::Pg include the segfault-on-text-insert fix
Tom provided.

 This means that as of now there is no obvious way to get a Perl5
driver that will work correctly with toasted fields in 7.1.  I have
emailed the maintainer (Edmund Mergl) twice in two weeks in an
attempt to get the patch applied, and he hasn't responded to either
of the emails, or any of the relevant threads on the DBI mailing
lists.

  What are the odds of getting DBD::Pg version 0.95 (the latest)
patched with Tom's fix, into the 7.1 release (maybe as an addition to
/src/interfaces/Perl5)? Can a new version of an interface library be
considered a bugfix if it does not work properly, as this one does
not? Or is it just too late in the cycle for his kind of addition (in
which case another method of access needs to be available)?

Jeff

-- 
 Jeff Duffy
 jeff@alanne.com