Question : identifying why a crash occurred

Running postgres 8.1 and rubyrep.

recently, we have crashed postgres multiple times. This is normally very stable environment. Only clue seems to be someone was doing pg_dump -s on db and rubyrep didn't like it? error is:

 ERROR:  permission denied for relation rr_running_flags
STATEMENT:  LOCK TABLE public.rr_running_flags IN ACCESS SHARE MODE

but this seems to come after it starts back up...

Any known bugs for rubyrep vs. pg_dump commands?

Answer : identifying why a crash occurred

Hi,
This turns out to be easy to replicate and has nothing in particular to do with ruby rep.

If I have a pg_hba file with both md5 and pam authentication lines, and the pam works for the user but there is no matching role, we get a crash.

This seems horrific, but we're dealing with it.