PgFoundry and External Projects
PostgreSQL is a complex software project,
and managing the project is difficult. We have found that many
enhancements to PostgreSQL can be more
efficiently developed separately from the core project.
To help our community with the development of their external projects,
we have created the PgFoundry.
PgFoundry is built using the
GForge software project and is similar to SourceForge in its feature set. If
you have a PostgreSQL related Open Source project that you would like to
develop and need project management resources such as mailing lists, forums,
bug tracking, and CVS, please feel free to create a new project.
Secondly, many PostgreSQL-related projects are
still hosted at GBorg>.
GBorg is the original external community developer site, and while it is
currently closed to new projects in favor of PgFoundry, it still contains
many active and relevant projects. There are other popular PostgreSQL
related projects that are hosted independently as well at other community
sites such as SourceForge. You should
search the web if you don't find the project you are looking for.
Externally Developed Interfaces
interfaces
PostgreSQL includes very few interfaces
with the base distribution. libpq> is packaged because
it is the primary C> interface and many other interfaces
are build on top of it. ecpg> is also packaged because it is
tied to the server-side grammar so is very dependent on the database
version. All the other interfaces, such as ODBC, Java, Perl, Python, and
others, are external projects and must be installed separately.
Some of the more popular interfaces are:
psqlODBC
This is the most common interface for Windows>
applications. Website.
ODBCng
Another ODBC driver for PostgreSQL.
Website.
PostgreSQL JDBC Driver
A JDBC> interface.
Website.
Npgsql
.Net> data provider for C#> applications.
Website.
libpqxx
A C++> interface.
Website.
DBD::Pg
A Perl> DBI driver for PostgreSQL.
Website.
pgtclng
A Tcl> interface.
Website.
pyscopg
A Python> interface library that is DB API 2.0 compliant.
Website.
Extensions
extensions
PostgreSQL> 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
contrib/> directory shipped with the source code
contains a large number of extensions. The README> file
in that directory contains a summary. They include conversion tools,
full-text indexing, XML> tools, and additional data types
and indexing methods. Other extensions are developed independently,
like PostGIS>. Even PostgreSQL>
replication solutions are developed externally. For example,
Slony-I> is a popular master/slave replication solution
that is developed independently from the core project.
There are several administration tools available for
PostgreSQL>. The most popular is
pgAdmin III>,
and there are several commercially available ones as well.