Re: Crash during elog.c...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Crash during elog.c...
Date: 2005-11-07 20:19:23
Message-ID: 28282.1131394763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jim C. Nasby" <jnasby(at)pervasive(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message karen hill 2005-11-07 21:04:48 DTrace?
Previous Message Gregory Maxwell 2005-11-07 20:07:15 Re: Interval aggregate regression failure (expected seems