Mathieu from INIBAP has found that the server can be knocked over by
trying to create a database when the database admin user does not
have its own database installation
While the argument that "why should a user account need its own
database" is absolutely true, there is in fact a tiny little bit of logic
behind this. The openSputnik installation that I run in Turku currently
holds 300 discrete sub-databases and these are spread over 3
postgresql database servers (and I have 2 development servers running
on mysql). Only one of these servers stores the core openSputnik
database, this alone cannot be used to control the federation of dbs.
To create or drop a database requires that we have a connection to the
postgresql server. This connection cannot be to the database that we
wish to drop, and unlike mysql, postgres does not support a
databaseless connection (e.g. Null) and does not by default install a
test database (while there are various template databases these are not
always available). This means that we need a database specifically for
the purpose of admininstrative connections, and this is something that
cannot be performed automatically because if you try to connect to
postgres it always assumes that unless otherwise specified that an
administrative user database will exist.