Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3D4ZE819535 for ; Fri, 13 Apr 2001 00:35:14 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3D4YWR02603; Fri, 13 Apr 2001 00:35:12 -0400 (EDT) To: "Jeff Duffy" cc: pgsql-interfaces@postgresql.org Subject: Re: Status of DBD:Pg and Pg interfaces for Perl In-reply-to: <200104081700.f38H09849242@postgresql.org> References: <200104081700.f38H09849242@postgresql.org> Comments: In-reply-to "Jeff Duffy" message dated "08 Apr 2001 12:00:11 -0400" Date: Fri, 13 Apr 2001 00:34:32 -0400 Message-ID: <2600.987136472@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/28 X-Sequence-Number: 1411 "Jeff Duffy" writes: > and neither Pg.pm or DBD::Pg include the segfault-on-text-insert fix > Tom provided. What? Are you claiming that Pg.pm has a segfault problem in the same area that DBD::Pg did? The code is sufficiently different that that would surprise me considerably. > 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)? Zip. We do not ship DBD::Pg as part of the Postgres distribution, and adding it now is not practical (makefile changes alone would create more breakage risk than I care to consider). If Edmund Mergl would like us to start shipping DBD::Pg in the distribution, then I'd certainly consider that for 7.2 and later. But right offhand, distributing it via CPAN seems to make more sense, since you'd have to go to CPAN for DBI anyway... regards, tom lane