Re: pg crashing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: pg crashing
Date: 2008-07-01 20:33:38
Message-ID: 19416.1214944418@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> writes:
> Version: "PostgreSQL 8.3.0, compiled by Visual C++ build 1400"

Well, there are plenty of known bugs in 8.3.0 by now. You really
should update before complaining, not after.

> Problem: My database keeps on crashing every few days with this type of
> error message:

> 2008-07-01 10:46:30 CDT LOG: all server processes terminated;
> reinitializing

I think your real problem is with what happened *before* that.
But:

> 2008-07-01 10:46:31 CDT FATAL: pre-existing shared memory block is
> still in use
> 2008-07-01 10:46:31 CDT HINT: Check if there are any old server
> processes still running, and terminate them.

Hmm ... the code in win32_shmem.c that generates this message seems
mighty bogus to me --- it's just hoping that one-second delay is
enough. Another problem is that postmaster children that do
PGSharedMemoryDetach will still have valid inherited handles for
the shmem segment --- does that factor into the behavior? It looks
to me like the CloseHandle ought to be in PGSharedMemoryDetach.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Magoffin 2008-07-01 20:38:08 Memory use in 8.3 plpgsql with heavy use of xpath()
Previous Message Roberts, Jon 2008-07-01 20:20:24 pg crashing

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2008-07-01 20:55:34 Re: Commitfest status?
Previous Message Roberts, Jon 2008-07-01 20:20:24 pg crashing