Comment 8 for bug 1273636

I discovered two different methods of issuing a 'reload', and I think what might be happening is the configuration reload is sometimes failing, but being repaired in a subsequent hook. This would create a window of time where the auth configuration is out of date.

I've been refactoring the service startup, stop & reload functionality. There is a reasonable chance it fixes the problem, and if not, at least improves the logging in this area and we can trace it further.

lp:~stub/charms/postgresql/pg93 contains the updates.