On Sun, Feb 7, 2010 at 12:00 AM, Josh Berkus wrote:
> On 2/6/10 8:20 PM, Robert Haas wrote:
>> On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef 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
>>>
On 2/6/10 8:20 PM, Robert Haas wrote:
> On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef 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
On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef 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
> 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.
It never actually crashed. And, of course, this was happening right
when I needed to go home and the server needed to be up for that.
On Fri, Feb 5, 2010 at 9:50 PM, The Fuzzy Chef wrote:
> Just had a very odd thing happen with an 8.4.2 database, and am
> concerned it's an undiagnosed bug:
>
> (1) created and dropped the same database 10-15 times in the course of
> running some tests.
>
> (2) at one point, dropdb hung. Indefini
