After the steps described in RHQ-438, my postgres server appeared as unavailable because the username/password were invalid. That is expected. What surprised me is that all of the postgres children still appear as available.
Description
After the steps described in RHQ-438, my postgres server appeared as unavailable because the username/password were invalid. That is expected. What surprised me is that all of the postgres children still appear as available.
Attached screenshot. I'm not sure how this happens, since I can't see how the query "SELECT COUNT(*) FROM PG_ROLES WHERE rolname = ?" can execute against the postgres instance if the username/password are invalid (again, see RHQ-438). In any event, this is confusing that the postgres instance itself is unavailable but all of its children are still available.
Jason Dobies - 04/May/08 11:40 AM Attached screenshot. I'm not sure how this happens, since I can't see how the query "SELECT COUNT(*) FROM PG_ROLES WHERE rolname = ?" can execute against the postgres instance if the username/password are invalid (again, see RHQ-438). In any event, this is confusing that the postgres instance itself is unavailable but all of its children are still available.
Bug
Accepted
Major
Postgres children still appear as available when postgres is marked as down
RHQ-438). In any event, this is confusing that the postgres instance itself is unavailable but all of its children are still available.