Re: Crash during elog.c...

"Jim C. Nasby" <jnasby@pervasive.com> writes:
> My client (same one with the slru.c issue) has had 3 of these in the
> past day...

> (gdb) print *str
> $39 = {data = 0x848030 "2005-11-04 00:01:02 EST|2005-11-04 00:00:08 EST|216.187.113.78(39476)|didit|", len = 76,
>   maxlen = 256, cursor = 0}

Um, what's your log_line_prefix setting, and is the next format code
%i by any chance?  I've just noticed an utterly brain-dead assumption
somebody stuck into ps_status.c awhile back.
        regards, tom lane