Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fARG6Fm99817 for ; Tue, 27 Nov 2001 11:06:15 -0500 (EST) (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.4/8.11.4) with ESMTP id fARG66k19199; Tue, 27 Nov 2001 11:06:06 -0500 (EST) To: Peter Eisentraut cc: Thomas Lockhart , pgsql-docs@postgresql.org Subject: Re: Documentation gap: Perl interfaces In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Tue, 27 Nov 2001 15:36:50 +0100" Date: Tue, 27 Nov 2001 11:06:06 -0500 Message-ID: <19196.1006877166@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/99 X-Sequence-Number: 1172 Peter Eisentraut writes: > We've been there, and it all that information became outdated pretty soon. > In fact we've just removed all not-included-here documentation in this > release. There are literally thousands of packages interfacing with > PostgreSQL, and I don't see how we're going to manage to put these into > the documentation. I agree that we shouldn't try to track the exact version, location, features, etc of outside packages --- but the *existence* of a DBI/DBD driver for Postgres strikes me as an important, and not unstable, piece of information. That's not "one package" that interfaces with Postgres, that's the foundation for countless applications. Right now, Perl people who come looking at the PG docs might well go away again feeling unwanted. That's bad for us in the long run. regards, tom lane