summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorOliver Charles <ollie@ocharles.org.uk>2014-04-06 12:00:02 +0100
committerOliver Charles <ollie@ocharles.org.uk>2014-04-06 12:38:02 +0100
commite2066841106a6b89093ab685368742efa4e3c2c1 (patch)
treee8b863d515acefea36c526aff0d3d490e3e2e50b /pkgs/development/python-modules/rangehttpserver
parent7de29bd26f5e514e95d5d261c08f3029337eecb3 (diff)
Use PostgreSQL 9.3's `pg_isready` to wait for connectivity
The postgresql module has a postStart section that waits for a database to accept connections before continuing. However, this assumes various properties about the database - specifically the database user and (implicitly) the database name. This means that for old installations, this command fails because there is no 'postgres' user, and the service never starts. While 7deff39 does create the 'postgres' user, a better solution is to use `pg_isready`, who's sole purpose is to check if the database is accepting connections. This has no dependency on users, so should be more robust.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions