On Sun, Feb 7, 2010 at 12:00 AM, Josh Berkus <j...@agliodbs.com> wrote: > On 2/6/10 8:20 PM, Robert Haas wrote: >> On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef <fu...@fuzzychef.org> wrote: >>>> It's too bad you didn't capture a stack backtrace at step #3 or step >>>> #6. If you manage to reproduce the problem, that would be a good >>>> thing to try to get. >>> Well, I never got an actual crash. >> >> That's OK - you can still attach gdb and see where it's hung up... it >> would have been really nice to see what that "hung" drop database >> thought it was doing... > > Yep, sorry. Was trying to get the system working first, and then > afterwards thought it might be worth reporting. > > Anything I can mine out of the logs or files?
I'm not familiar enough to say; but I wonder if you could try to reproduce the problem on (a copy of) your saved directory. ...Robert -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
