"Chris Ochs" <[EMAIL PROTECTED]> writes:
>> I think that we're trying to report the current session authorization to
>> the client (which is something that happens automatically on any change)
>> and it's referencing a deleted user. Is it possible that your setup is
>> deleting the user that the e
>
> > (gdb) bt
> > #0 0x284f9dcf in kill () from /lib/libc.so.5
> > #1 0x284ee878 in raise () from /lib/libc.so.5
> > #2 0x28566f82 in abort () from /lib/libc.so.5
> > #3 0x08226a6a in errfinish ()
> > #4 0x08226953 in errfinish ()
> > #5 0x0822f54d in GetUserNameFromId ()
> > #6 0x081183a3
"Chris Ochs" <[EMAIL PROTECTED]> writes:
ERROR: invalid user ID: 194
PANIC: error during error recovery, giving up
LOG: server process (PID 38302) was terminated by signal 6
Can you get a stack traceback from this crash? The only occurrence of
"invalid user ID:" that I see in the source code i
"Chris Ochs" <[EMAIL PROTECTED]> writes:
> ERROR: invalid user ID: 194
> PANIC: error during error recovery, giving up
> LOG: server process (PID 38302) was terminated by signal 6
Can you get a stack traceback from this crash? The only occurrence of
"invalid user ID:" that I see in the source
I have been able to crash the server a few times with the following function
when it is called on a user and schema that was recently deleted. Following
is a log of what happened and also the function that was called. This is
7.4.3 on Freebsd 5.2.1. It doesn't always panic when it encounters a
