LogoopenSUSE Build Service > Projects
Sign Up | Log In

A Connection Pooling/Replication Server for PostgreSQL

pgpool-II is a middleware that works between PostgreSQL servers and a PostgreSQL database client. It provides the following features.

    * Connection Pooling

      pgpool-II saves connections to the PostgreSQL servers, and reuse them whenever a new connection with the same properties (i.e. username, database, protocol version) comes in. It reduces connection overhead, and improves system's overall throughput.
    * Replication

      pgpool-II can manage multiple PostgreSQL servers. Using the replication function enables creating a realtime backup on 2 or more physical disks, so that the service can continue without stopping servers in case of a disk failure.
    * Load Balance

      If a database is replicated, executing a SELECT query on any server will return the same result. pgpool-II takes an advantage of the replication feature to reduce the load on each PostgreSQL server by distributing SELECT queries among multiple servers, improving system's overall throughput. At best, performance improves proportionally to the number of PostgreSQL servers. Load balance works best in a situation where there are a lot of users executing many queries at the same time.
    * Limiting Exceeding Connections

      There is a limit on the maximum number of concurrent connections with PostgreSQL, and connections are rejected after this many connections. Setting the maximum number of connections, however, increases resource consumption and affect system performance. pgpool-II also has a limit on the maximum number of connections, but extra connections will be queued instead of returning an error immediately.
    * Parallel Query

      Using the parallel query function, data can be divided among the multiple servers, so that a query can be executed on all the servers concurrently to reduce the overall execution time. Parallel query works the best when searching large-scale data.

pgpool-II talks PostgreSQL's backend and frontend protocol, and relays a connection between them. Therefore, a database application (frontend) thinks that pgpool-II is the actual PostgreSQL server, and the server (backend) sees pgpool-II as one of its clients. Because pgpool-II is transparent to both the server and the client, an existing database application can be used with pgpool-II almost without a change to its sources.

Source Files (show merged sources derived from linked package)

Filename Size Changed Actions
_multibuild 197 Bytes 12 months ago Download File
pgpool-II-3.6.1_implicit.patch 502 Bytes 12 months ago Download File
pgpool-II-3.6.5.tar.gz 2.53 MB 12 months ago Download File
pgpool-II.changes 52.2 KB 10 months ago Download File
pgpool-II.init 11.4 KB over 7 years ago Download File
pgpool-II.service 360 Bytes over 3 years ago Download File
pgpool-II.spec 11.4 KB 10 months ago Download File
pgpool-II.sysconfig 333 Bytes over 7 years ago Download File
pgpool-II.tmpfiles.d 121 Bytes over 3 years ago Download File
pgpool-II_conf.patch 10.4 KB 12 months ago Download File
pgpool-ha-3.0.tar.bz2 5.09 KB about 2 years ago Download File
pgpoolAdmin-3.6.1.tar.gz 1 MB 12 months ago Download File
postgresql-pgpool-II.spec.in 3.42 KB 12 months ago Download File

Comments for home:azouhr:zhub (0)