| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | god(at)yinyang(dot)hjsoft(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Posgresql 7.2b1 crashes |
| Date: | 2001-11-01 16:49:28 |
| Message-ID: | 22185.1004633368@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mr. Shannon Aldinger" <god(at)yinyang(dot)hjsoft(dot)com> writes:
> I've had two overnight crashes with postgresql-7.2b1. Neither logged any
> useful info in the logfile created by pg_ctl, syslog or messages.
Please define "crash". If it was a coredump, how about a stack
backtrace? Can you determine what query it was executing?
While I'd like to help you, you have not provided one single bit of
information that could possibly be used to identify the problem ...
> glibc-2.2.x.
... except perhaps that. If you compiled with --enable-locale, an
update to glibc 2.2.3 is strongly advised. There's a nasty bug in
strcoll() in 2.2.x.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2001-11-01 17:11:05 | Re: Serious performance problem |
| PostgreSQL : 토토 결과보기 | Cyril VELTER | 2001-11-01 16:40:46 | PostgreSQL : 토토 결과보기 최적화 |