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-05 01:06:39
Message-ID: 19135.1131152799@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:
> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Qingqing Zhou 2005-11-05 02:36:44 Re: Possible problem with pg_reload_conf() and view pg_settings
Previous Message Marc G. Fournier 2005-11-05 00:46:27 Re: Assert failure found in 8.1RC1