From: Thomas Haegi <me@alternize.com>
To: pgsql-bugs@postgresql.org
Subject: BUG #3767: tsearch2 index creation fatal crash
Date: Wed, 21 Nov 2007 02:25:14 GMT
Message-ID: <200711210225.lAL2PE8a064911@wwwmaster.postgresql.org> (raw)
The following bug has been logged online:
Bug reference: 3767
Logged by: Thomas Haegi
Email address: me@alternize.com
PostgreSQL version: 8.3b3
Operating system: Windows 2003
Description: tsearch2 index creation fatal crash
Details:
the previously reported problem gets worse if you execute the query 2-3
times... postgres.exe terminates:
Faulting application postgres.exe, version 8.3.0.7319, faulting module
postgres.exe, version 8.3.0.7319, fault address 0x001ced2f.
from the pgsql logs:
2007-11-21 03:24:40 CET LOG: server process (PID 2376) exited with exit
code 128
2007-11-21 03:24:40 CET LOG: terminating any other active server processes
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET WARNING: terminating connection because of crash of
another server process
2007-11-21 03:24:40 CET DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2007-11-21 03:24:40 CET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2007-11-21 03:24:40 CET LOG: all server processes terminated;
reinitializing
2007-11-21 03:24:41 CET FATAL: pre-existing shared memory block is still in
use
2007-11-21 03:24:41 CET HINT: Check if there are any old server processes
still running, and terminate them.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: me@alternize.com, pgsql-bugs@postgresql.org
Subject: Re: BUG #3767: tsearch2 index creation fatal crash
In-Reply-To: <200711210225.lAL2PE8a064911@wwwmaster.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox