From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "otisg" <otisg(at)iVillage(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Dying PostgreSQL backend |
Date: | 2002-05-06 13:45:31 |
Message-ID: | 4845.1020692731@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"otisg" <otisg(at)iVillage(dot)com> writes:
> What gets logged in syslog log file are things like this:
The messages you quoted are no help, because none of them directly
show the crashing backend.
What I'd recommend doing is gdb'ing the core dump file to get a stack
trace; that would give us some clue what's wrong. And you could do
"p debug_query_string" to see what query made it crash.
If you do not find a core file in the database subdirectory
($PGDATA/base/yourdbnumber/core) then you are probably running the
postmaster with "ulimit -c 0" which disables core dumps. Restart
it with environment "ulimit -c unlimited".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark McEahern | 2002-05-06 14:23:11 | Re: configure datatype name > 31? |
Previous Message | Rajesh Kumar Mallah. | 2002-05-06 13:26:10 | Re: SERIAL Field |