Hi The O/S is Win 2K Server SP4 and PG version is 8.0. Here's the log file from the latest incident: 2006-06-16 09:40:01 LOG: 0: server process (PID 4744) was terminated by signal 125 2006-06-16 09:40:01 LOCATION: LogChildExit, postmaster.c:2335 2006-06-16 09:40:01 LOG: 0: ter
On Thursday 25 May 2006 10:47, chelsea boot wrote:
> Hi
>
> Can anyone offer advice on this please: Intermittently a postgres process
> appears to crash and the postmaster service needs restarting. The
> following is entered in the log:
>
> 2006-03-15 09:50:03 LOG: server process (PID 348) wa
Hi Can anyone offer advice on this please: Intermittently a postgres process appears to crash and the postmaster service needs restarting. The following is entered in the log: 2006-03-15 09:50:03 LOG: server process (PID 348) was terminated by signal 125 2006-03-15 09:50:03 LOG: termina
After reproducing these crashes and running tests long enough, we found
that these Postgres Crashes happen on linux 2.4.18 and not on linux
2.4.25. In all likelihood, this is a kernel (or driver) issue.
Could you kindly ensure this gets on my mail thread with subject "Postgres
Crashes".
Thanks
P
This sounds very much like a memory problem. I would replace all of
the memory with another set of (preferably known good) memory and see
if the problems persist. Also look for other cores that may be
dropped. If there are several, memory is the likely cause. Be aware
that it will likely
[EMAIL PROTECTED] (Prem Gopalan) writes:
> The dying process is postmaster. After these crashes the server is
> missing from ps and no more new connections are possible. The backend
> processes stay on till their connections close.
That behavior does sound like a postmaster crash --- but all the s
Prem Gopalan wrote:
> We run a multithreaded application that uses postgres 7.4 on Linux
> 2.4.18, dual cpu Xeon processor machine. We have occassional weird
> crashes and have tried a lot of things to reproduce them in house, but
> in vain. We do have coredumps and I have listed the backtraces and
We run a multithreaded application that uses postgres 7.4 on Linux
2.4.18, dual cpu Xeon processor machine. We have occassional weird
crashes and have tried a lot of things to reproduce them in house, but
in vain. We do have coredumps and I have listed the backtraces and
their common characteristic
