From: | "Maksim Likharev" <mlikharev(at)aurigin(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] PG crash on simple query, story continues |
Date: | 2003-07-12 23:59:21 |
Message-ID: | 56510AAEF435D240958D1CE8C6B1770A014A0E28@mailc03.aurigin.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Possible, but if before almost every tenth query crash the server
now it stays, that's only I care about.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Saturday, July 12, 2003 2:05 PM
To: Maksim Likharev
Cc: pgsql-general(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] [GENERAL] PG crash on simple query, story
continues
"Maksim Likharev" <mlikharev(at)aurigin(dot)com> writes:
> So following modification seems to fixed all PG (7.3/7.3.3)crashes on
> Solaris ( NON C LOCALE )
Given that the problem is Solaris' tendency to write more data than
the specified output buffer length allows, I'd think this is still
risking a core dump (due to null pointer dereference).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-07-13 02:25:32 | Re: vacuum analyze after updating from CVS? |
Previous Message | Jim C. Nasby | 2003-07-12 23:05:22 | Re: [GENERAL] MySQL gets $19.5 MM |
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2003-07-13 00:01:26 | Re: weird problem |
Previous Message | Francisco Figueiredo Jr. | 2003-07-12 23:52:04 | Re: Handling protocol not supported error message when |