Re: BUG #3767: tsearch2 index creation fatal crash - Mailing list pgsql-bugs

the reported problem below can be reproduced by using this simple query
straight from the documentation:

SELECT to_tsvector('a fat cat sat on a mat and ate a fat rat');

--> postgres.exe dies instantly, with the logs being the same as in the
bugreport.



interestingly using ::tsvector (which according to the documentation is
equivalent) works just fine:

SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector;

gives the correct result.

default configuration for text search is set to:
default_text_search_config = 'pg_catalog.german'


- thomas



-------- Original Message --------
Subject: [BUGS] BUG #3767: tsearch2 index creation fatal crash
From: Thomas Haegi <me@alternize.com>
To: pgsql-bugs@postgresql.org
Date: 21.11.2007 03:25

> 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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly