pgpool-II allows multiple PostgreSQL servers (DB nodes) to be
connected, which enables queries to be executed simultaneously on all
servers.
It enables "parallel query" processing. Also, pgpool-II can be started
as pgpool-I by changing configuration parameters. pgpool-II that is
executed in pgpool-I mode enables multiple DB nodes to be connected,
which was not possible in pgpool-I.
pgpool-II allows multiple PostgreSQL servers (DB nodes) to be
connected, which enables queries to be executed simultaneously on all
servers.
It enables "parallel query" processing. Also, pgpool-II can be started
as pgpool-I by changing configuration parameters. pgpool-II that is
executed in pgpool-I mode enables multiple DB nodes to be connected,
which was not possible in pgpool-I.
pgpool is a connection pool server for PostgreSQL. pgpool runs between
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL client can
connect to pgpool as if it were a standard PostgreSQL server.
pgpool caches the connection to PostgreSQL server to reduce the overhead to
establish the connection to it.
Web-based administration tool for pgpool-II.
pgreplay reads a PostgreSQL log file (*not* a WAL file), extracts the
SQL statements and executes them in the same order and with the original
timing against a PostgreSQL database.
pgSphere provides spherical data types, functions, and operators for PostgreSQL.
pgtop was inspired by mytop (http://jeremy.zawodny.com/mysql/mytop/),
which in turn was inspired by the system monitoring tool top.
pgtop will connect to a PostgreSQL server and periodically
run queries against the pg_stat* relations and attempt
to summarize the information from them in a useful format.
pgtune takes the wimpy default postgresql.conf and expands
the database server to be as powerful as the hardware it's
being deployed on.
URI datatype for PostgreSQL
This extension is a PHP binding for Google LevelDB