The database_server role currently uses password-based authentication for the root user, limiting authentication to localhost. Since the database_server is only ever used from the same server, though, it would be beneficial to get rid of password-based authentication for the root user, and to rely on the unix socket authentication instead.

This would both reduce number of passwords used, as well as make the root database user logins safer (since it would prevent other processes from logging-in as root user provided they can guess the password).

The following should be done:

• Update the database_server role.
  • Drop the db_root_password parameter.
  • Switch to using the unix socket authentication for the root user.
  • Make sure the user is set-up correctly and that the root user cannot login without providing any kind of credentials/authentication.
  • There is also a TODO entry in the role tasks that should be taken care of.
• Update tests. Pay attention to tests for roles that use the database_server role directly/indirectly.
• Update test site configuration.
• Update usage instructions.
• Update role reference.
• Update release notes.