7de29bd26f
Old PostgreSQL installations were created using the 'root' database user. In this case, we need to create a new 'postgres' account, as we now assume that this is the superuser account. Unfortunately, these machines will be left with a 'root' user as well (which will have ownership of some databases). While PostgreSQL does let you rename superuser accounts, you can only do that when you are connected as a *different* database user. Thus we'd have to create a special superuser account to do the renaming. As we default to using ident authentication, we would have to create a system level user to do this. This all feels rather complex, so I'm currently opting to keep the 'root' user on these old machines. |
||
|---|---|---|
| .. | ||
| 4store-endpoint.nix | ||
| 4store.nix | ||
| couchdb.nix | ||
| firebird.nix | ||
| memcached.nix | ||
| mongodb.nix | ||
| mysql.nix | ||
| openldap.nix | ||
| postgresql.nix | ||
| redis.nix | ||
| virtuoso.nix | ||