This commit was manufactured by cvs2svn to create branch

'REL-1_2_0_PATCHES'. git-svn-id: svn://svn.pgadmin.org/branches/REL-1_2_0_PATCHES@4045 a7884b65-44f6-0310-8a51-81a127f17b15
pgadmin-org · Mar 26, 2005 · abe8e53 · abe8e53
1 parent 5a21028
commit abe8e53
Show file tree

Hide file tree

Showing 6 changed files with 1,900 additions and 0 deletions.
diff --git a/docs/en_US/pg/external-extensions.html b/docs/en_US/pg/external-extensions.html
@@ -0,0 +1,38 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>H.2. Extensions</title>
+<link rel="stylesheet" href="stylesheet.css" type="text/css">
+<link rev="made" href="pgsql-docs@postgresql.org">
+<meta name="generator" content="DocBook XSL Stylesheets V1.64.1">
+<link rel="home" href="index.html" title="PostgreSQL 8.1devel Documentation">
+<link rel="up" href="external-projects.html" title="Appendix H. External Projects">
+<link rel="previous" href="external-projects.html" title="Appendix H. External Projects">
+<link rel="next" href="biblio.html" title="Bibliography">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
+<div class="titlepage">
+<div><div><h2 class="title" style="clear: both">
+<a name="external-extensions"></a>H.2. Extensions</h2></div></div>
+<div></div>
+</div>
+<a name="id2786879"></a><p>   <span class="productname">PostgreSQL</span> was designed from the start to be
+   extensible. For this reason, extensions loaded into the database can
+   function just like features that are packaged with the database. The
+   <tt class="filename">contrib/</tt> directory shipped with the source code
+   contains a large number of extensions. The <tt class="filename">README</tt> file
+   in that directory contains a summary. They include conversion tools,
+   full-text indexing, <span class="acronym">XML</span> tools, and additional data types
+   and indexing methods. Other extensions are developed independently,
+   like <span class="application">PostGIS</span>. Even <span class="application">PostgreSQL</span>
+   replication solutions are developed externally. For example,
+   <span class="application">Slony-I</span> is a popular master/slave replication solution
+   that is developed independently from the core project.
+  </p>
+<p>   There are several administration tools available for
+   <span class="productname">PostgreSQL</span>. The most popular is
+   <span class="application">pgAdmin</span>, and there are several commercially
+   available ones.
+  </p>
+</div></body>
+</html>
diff --git a/docs/en_US/pg/external-projects.html b/docs/en_US/pg/external-projects.html
@@ -0,0 +1,107 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<title>Appendix H. External Projects</title>
+<link rel="stylesheet" href="stylesheet.css" type="text/css">
+<link rev="made" href="pgsql-docs@postgresql.org">
+<meta name="generator" content="DocBook XSL Stylesheets V1.64.1">
+<link rel="home" href="index.html" title="PostgreSQL 8.1devel Documentation">
+<link rel="up" href="appendixes.html" title="Part VIII. Appendixes">
+<link rel="previous" href="docguide-style.html" title="G.5. Style Guide">
+<link rel="next" href="external-extensions.html" title="H.2. Extensions">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="appendix" lang="en" id="external-projects">
+<div class="titlepage">
+<div><div><h2 class="title">
+<a name="external-projects"></a>Appendix H. External Projects</h2></div></div>
+<div></div>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="sect1"><a href="external-projects.html#external-interfaces">H.1. Externally Developed Interfaces</a></span></dt>
+<dt><span class="sect1"><a href="external-extensions.html">H.2. Extensions</a></span></dt>
+</dl>
+</div>
+<p>   <span class="productname">PostgreSQL</span> is a complex software project,
+   and managing it is difficult. We have found that many
+   enhancements to <span class="productname">PostgreSQL</span> can be more
+   efficiently developed separately from the core project. Separate
+   projects can
+   have their own developer teams, email lists, bug tracking,
+   and release schedules. While their independence makes
+   development easier, it makes users' jobs harder. They have to hunt
+   around looking for database enhancements to meet their needs.
+   This section describes some of the more popular externally
+   developed enhancements and guides you on how to find them.
+  </p>
+<p>   Many <span class="productname">PostgreSQL</span>-related projects are
+   hosted at either
+   <span class="productname">GBorg</span> at <a href="http://gborg.postgresql.org" target="_top">http://gborg.postgresql.org</a>
+   or <span class="productname">pgFoundry</span> at <a href="http://pgfoundry.org" target="_top">http://pgfoundry.org</a>.
+   There are other
+   <span class="productname">PostgreSQL</span>-related projects that are hosted
+   elsewhere, but you will have to do an Internet search to find them.
+  </p>
+<div class="sect1" lang="en">
+<div class="titlepage">
+<div><div><h2 class="title" style="clear: both">
+<a name="external-interfaces"></a>H.1. Externally Developed Interfaces</h2></div></div>
+<div></div>
+</div>
+<a name="id2786646"></a><p>   <span class="productname">PostgreSQL</span> includes very few interfaces
+   with the base distribution. <span class="application">libpq</span> is packaged because
+   it is the primary <span class="application">C</span> interface and many other
+   interfaces are built on top of it. <span class="application">ecpg</span> is packaged
+   because it is tied to the server-side grammar so is very dependent
+   on the database version. All the other interfaces are independent
+   projects and must be installed separately.
+  </p>
+<p>   Some of the more popular interfaces are:
+
+   </p>
+<div class="variablelist"><dl>
+<dt><span class="term">psqlODBC</span></dt>
+<dd><p>       This is the most common interface for <span class="application">Windows</span>
+       applications.
+      </p></dd>
+<dt><span class="term">pgjdbc</span></dt>
+<dd><p>       A <span class="application">JDBC</span> interface.
+      </p></dd>
+<dt><span class="term">Npgsql</span></dt>
+<dd><p>       <span class="application">.Net</span> interface for more recent
+       <span class="application">Windows</span> applications.
+      </p></dd>
+<dt><span class="term">libpqxx</span></dt>
+<dd><p>       A newer <span class="application">C++</span> interface.
+      </p></dd>
+<dt><span class="term">libpq++</span></dt>
+<dd><p>       An older <span class="application">C++</span> interface.
+      </p></dd>
+<dt><span class="term">pgperl</span></dt>
+<dd><p>       A <span class="application">Perl</span> interface with an <span class="acronym">API</span> similar
+       to <span class="application">libpq</span>.
+      </p></dd>
+<dt><span class="term">DBD-Pg</span></dt>
+<dd><p>       A <span class="application">Perl</span> interface that uses the
+       <span class="acronym">DBD</span>-standard <span class="application">API</span>.
+      </p></dd>
+<dt><span class="term">pgtclng</span></dt>
+<dd><p>       A newer version of the <span class="application">Tcl</span> interface.
+      </p></dd>
+<dt><span class="term">pgtcl</span></dt>
+<dd><p>       The original version of the <span class="application">Tcl</span> interface.
+      </p></dd>
+<dt><span class="term">PyGreSQL</span></dt>
+<dd><p>       A <span class="application">Python</span> interface library.
+      </p></dd>
+</dl></div>
+<p>
+
+   All of these can be found at 
+   <span class="productname">GBorg</span> (<a href="http://gborg.postgresql.org" target="_top">http://gborg.postgresql.org</a>)
+   or <span class="productname">pgFoundry</span> (<a href="http://pgfoundry.org" target="_top">http://pgfoundry.org</a>).
+   </p>
+</div>
+</div></body>
+</html>