pgdbpool 0.97rc1

A tiny database de-multiplexer primarily scoped for Web- / Application Server.

Python PgDatabase-Pool Module

1. Primary Scope

The pgdbpool Python Module is a tiny PostgreSQL Database Connection De-Multiplexer primarily scoped for Web- / Application Server.

2. Current Implementation

+----------------------+                         +--------------- -  -   -
| WebServer Service.py | -- Handler Con #1 ----> | PostgreSQL 
| Request / Thread #1  |                         | Backend
+----------------------+                         |
                                                 |
+----------------------+                         |
| WebServer Service.py | -- Handler Con #2 ----> | 
| Request / Thread #2  |                         |
+----------------------+                         +--------------- -  -   -

2.1. Concept / Simplicity

If configured in a Web-Servers WSGI Python Script, the Pooling-Logic is quite simple.

1. Check if a free connection in the pool exists
2. Check if connection usable (SQL ping)
3. Use connection and protect it from beeing used until querie(s) finished
4. Release connection for usage again
5. Try reconnecting to endpoint if connection has been lost

3. Thread Safety / Global Interpreter Lock

Currently Thread Safety is guaranteed by lock = threading.Lock() which implies a Kernel Mutex syscall().

The concept works, but the GIL (Python Global Interpreter Lock) thwarts our plans 😞.

In detail: if used in a threaded Web-Server setup, it does not really scale well on heavy loads.

[!IMPORTANT] Take a closer look at "6. Future", problem solved probably.

4. Dependencies / Installation

Python 3 and psycopg2 module is required.

# apt-get install python3-psycopg2
# pip install pgdbpool

5. Documentation / Examples

See documentation ./doc for detailed explanation / illustrative examples.

6. Future

DB-Pooling also should be usable in FalconAS Python Application Server (https://github.com/WEBcodeX1/http-1.2/).

The model here: 1 Process == 1 Python Interpreter (threading-less), GIL Problem solved :grin:.

[!NOTE] Also a Pool should be configurable to use multiple (read-loadbalanced) PostgreSQL Endpoints.