On Jan 25, 2008 11:08 AM, David JL Gradwell [EMAIL PROTECTED] wrote:
I also noticed whilst I was doing the original 8.3rc2 install that I could
not specify PL/Java as a language to enable in the default database - see
screenshot.
Ahh - now that's most likely the problem. The installer only
Chris Hoover escribió:
Unfortunately, I can't find anything more for this error. There are no core
files, and no unexpected error entries in the postgres log files (running
syslog and csvlog). I really wish I could provide more, but I just went to
that terminal, and that line was there.
Chris Hoover [EMAIL PROTECTED] writes:
#3 0x082c8fa6 in ExceptionalCondition (
conditionName=0x83bc514 !(((header-context) != ((void *)0)
(Node*)((header-context)))-type) == T_AllocSetContext,
errorType=0x82f89d2 BadArgument, fileName=0xd3f , lineNumber=0) at
assert.c:57
#4
On Jan 25, 2008 2:23 PM, Tom Lane [EMAIL PROTECTED] wrote:
Chris Hoover [EMAIL PROTECTED] writes:
In the noon log, I have this entry:
2008-01-25 12:00:00.063 EST,,,3040,,479a01f1.be0,2,,2008-01-25 10:36:17
EST,,0,LOG,0,system logger process (PID 3041) was terminated by
signal
6:
On Jan 24, 2008 9:39 PM, Gurjeet Singh [EMAIL PROTECTED] wrote:
It sure looks like Postgres's ASSERT failure. And mcxt.c is Postgres'
memory management module.
Can you please figure out, and try to reproduce what were you (or your
app) doing when this happened.
Best regards,
On Jan
The following bug has been logged online:
Bug reference: 3902
Logged by: Peter Koczan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC2
Operating system: Red Hat Enterprise Linux 5
Description:Segmentation faults using GSSAPI authentication
Details:
On Jan 25, 2008 2:30 PM, Chris Hoover [EMAIL PROTECTED] wrote:
On Jan 25, 2008 2:23 PM, Tom Lane [EMAIL PROTECTED] wrote:
Chris Hoover [EMAIL PROTECTED] writes:
In the noon log, I have this entry:
2008-01-25 12:00:00.063 EST,,,3040,,479a01f1.be0,2,,2008-01-25
10:36:17
Peter Koczan [EMAIL PROTECTED] writes:
Trying to connect via GSSAPI (with Kerberos 5 as the underlying mechanism)
after the server has been under a very slight load results in an unusable
but still running server.
Can you get us a stack trace from that crash?
regards,
