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.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:database:postgresql/pgpool-II && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
pgpool-II-3.2.1.tar.gz | 0001605959 1.53 MB | |
pgpool-II.changes | 0000014073 13.7 KB | |
pgpool-II.init | 0000011723 11.4 KB | |
pgpool-II.spec | 0000007013 6.85 KB | |
pgpool-II.sysconfig | 0000000333 333 Bytes | |
pgpool-II_conf.patch | 0000008307 8.11 KB |
Revision 14 (latest revision is 71)
- update to 3.2.1 see /usr/share/doc/packges/pgpool-II/NEWS for the details - use postgresql 9.2 to build against
Comments 4
Could you please update pgpool-II to version 4.2.2. Thank you in advance. Best Regards, Ralf
The service file needs following update in Unit section: Wants=postgresql.service After=postgresql.service
Basically: [Unit] Description=PGPool-II Middleware Between PostgreSQL Servers And PostgreSQL Database Clients After=syslog.target network.target Wants=postgresql.service After=postgresql.service
[Service] User=pgpool Group=pgpool
EnvironmentFile=-/etc/sysconfig/pgpool
ExecStart=/usr/sbin/pgpool -n -f /etc/pgpool-II/pgpool.conf ExecReload=/usr/sbin/pgpool reload Restart=always
[Install] WantedBy=multi-user.target
submitted package update
for some reason my submit was revoked and I have no idea how to go on. if somebody wants to test out my build, it is under derived packages: https://build.opensuse.org/package/show/home:Mihail-Klr:branches:server:database:postgresql/pgpool-II