Remove mention of DBD::PgSPI, which is unmaintained and generally unnecessary.

diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
index ce217dfa33ba55546138ff24214f1eab5f2455d0..dfb15b3bd172d6d8e8d96bab61db4f4a9018823a 100644 (file)
--- a/doc/src/sgml/plperl.sgml
+++ b/doc/src/sgml/plperl.sgml
@@ -1,4 +1,4 @@
-
+
 
  
   PL/Perl - Perl Procedural Language
@@ -309,20 +309,7 @@ BEGIN { strict->import(); }
 
   
    Access to the database itself from your Perl function can be done
-   via the function spi_exec_query described
-   below, or via an experimental module 
-   
-   DBD::PgSPI
-   (also available at 
-   CPAN mirror sites).  This module makes available a
-   DBI-compliant database-handle named
-   $pg_dbh that can be used to perform queries with
-   normal DBI
-   syntax.DBI
-  
-
-  
-   PL/Perl provides additional Perl commands:
+   via the following functions:
 
    
     
@@ -412,6 +399,7 @@ $$ LANGUAGE plperl;
 SELECT * FROM test_munge();
 
     
+
     
     spi_query and spi_fetchrow
     work together as a pair for row sets which might be large, or for cases