We should upgrade our main postgresql install to 9.5, now that the final version has been released.
Considering our current space usage, we should probably do a database-per-database upgrade.
We should probably use this opportunity to setup pgpool or another connection proxy in front of the main databases.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T262 Upgrade postgresql to 9.5 | ||
| Migrated | gitlab-migration | T266 Setup pgbouncer on prado | ||
| Migrated | gitlab-migration | T267 Migrate databases to postgres 9.5 |
The latest pgbouncer release (1.7) supports TLS, hba and unix peer authentification so looks like a good candidate. I submitted a bug to Debian to ask for an update of the package : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810816
Agreed, pgbouncer would be nice (and IIRC also the choice that Dimitri recommended to us a while back).
While we are at it, I also wonder if we should consider moving some databases to a different cluster, not backed by SSD disks. While both swh and swh-log DBs can stay on the main cluster for now, I guess all "mirror" DBs (e.g., snapshot.d.o, antelink, etc.) might go to a different DB, possibly even on banco.
That sounds sensible. We should be able to export a LV from our spinning rust storage to prado for that "mirrors" postgresql cluster.
To be honest, I'm not even sure that having swh-log or even the swh snapshot databases on the same cluster as the main database is sensible. We don't care about point in time recovery for those, and we don't really want the tests we're doing there to affect what's going on in the main database.
I'd be in favor of working with three clusters then:
And putting pgbouncer on top of that to smooth things out.
PostgreSQL has now been updated to 9.5 (and split into three clusters).
PgBouncer has been setup on port 5432 and proxies to the three clusters transparently.