Re: Crash during elog.c... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Crash during elog.c...
Date
Msg-id 28282.1131394763@sss.pgh.pa.us
Whole thread Raw
In response to Re: Crash during elog.c...  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> On Fri, Nov 04, 2005 at 08:06:39PM -0500, Tom Lane wrote:
>> 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.

> log_line_prefix = '%t|%s|%r|%d|%i|%p'

> So yeah, looks like %i is next.

The quickest way to get rid of the crash will be to remove %i, then.
If you don't want to do that, see the patch I committed to CVS.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Maxwell
Date:
Subject: Re: Interval aggregate regression failure (expected seems
Next
From: Marc Munro
Date:
Subject: Odd db lockup - investigation advice wanted