[Please don't top-post. http://idallen.com/topposting.html ]
"umashankar narayanan" <umashankar@graffiti.net> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:
>> "umashankar narayanan" <umashankar@graffiti.net> wrote:
>> Please give the full version
> The full version of Postgres is 8.3.1.
You are missing four years of bug fixes for 8.3.
http://www.postgresql.org/support/versioning/
To see what fixes you are missing, look at the links to release
notes for 8.3.2 to 8.3.18:
http://www.postgresql.org/docs/8.3/static/release.html
Please either update to a recent bug-fix release of 8.3 or review
all of these pages closely to be sure that your problem couldn't
have been caused by any of the already-fixed bugs.
>>> 2012-03-07 11:57:20 EST LOG: server process (PID 5944) exited
>>> with exit code 128
>>
>> Was there anything in the PostgreSQL log ahead of this to give a
>> clue what went wrong and caused this?
> All that I see on the postgres log before the crash is the below
> message:
>
> 2012-03-07 11:56:12 EST LOG: loaded library
> "$libdir/plugins/plugin_debugger.dll"
That's about one minute before the crash. If that's not what caused
the crash, it's a heck of a coincidence.
>>> 2012-03-07 11:57:22 EST FATAL: pre-existing shared memory block
>>> is still in use
>>> 2012-03-07 11:57:22 EST HINT: Check if there are any old server
>>> processes still running, and terminate them.
>>
>> Something is still hanging on to the PostgreSQL shared memory
>> block.
>>
>> Are any postgres processes lingering? Are you running anything
>> else which might be grabbing the same shared memory block?
> No other postgres processes are lingering. I did confirm that no
> other batch jobs or monitoring jobs were running during this time,
> that would grab the same shared memory block.
Perhaps the debugger still had some process active and attached to
shared memory at the point that this was logged, but has since
released the memory? *Something* was still using PostgreSQL shared
memory at 2012-03-07 11:57:22 EST.
-Kevin