tsearch - Regression tests fail

Hello!

I tried the regression tests for contrib/tsearch as suggested, and this
leads to exactly the same symptoms as described with the real-life test.
The last entry of regression.diffs reads:

  select '1'::mquery_txt;
! server closed the connection unexpectedly
!       This probably means the server terminated abnormally
!       before or while processing the request.
! connection to server was lost

Any ideas?

Regards,

    Markus

> -----Ursprungliche Nachricht-----
> Von: Markus Wollny
> Gesendet: Montag, 29. Juli 2002 13:52
> An: pgsql-general@postgresql.org
> Cc: Oleg Bartunov
> Betreff: Re: [GENERAL] Using FTI-Search (likely a more
> general runtime-puzzle)
>
>
> Hi!
>
> I am about to evaluate the tsearch module from contrib, but as yet I
> haven't succeeded in getting it to run.
>
> I followed instructions on installation of tsearch; the new
> datatype and
> the corresponding functions seem all to be there. So I want to try it
> out on some existing data. In table article I want to set up
> a full-text
> index on column text. After adding the column textindex of
> type txtidx,
> I try to fill that column with data, but this just crashes the backend
> immediately:
>
> pcgames=# update article set textindex=txt2txtidx(text);
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
>
> The logfile doesn't really give much information on what exactly
> happened:
>
> 2002-07-29 13:37:20 [22127]  DEBUG:  database system is ready
> 2002-07-29 13:37:46 [22124]  DEBUG:  server process (pid 22137) was
> terminated by signal 11
> 2002-07-29 13:37:46 [22124]  DEBUG:  terminating any other
> active server
> processes
> 2002-07-29 13:37:46 [22124]  DEBUG:  all server processes terminated;
> reinitializing shared memory and semaphores
> 2002-07-29 13:37:46 [22139]  FATAL 1:  The database system is starting
> up
> 2002-07-29 13:37:46 [22138]  DEBUG:  database system was
> interrupted at
> 2002-07-29 13:37:20 CEST
> 2002-07-29 13:37:46 [22138]  DEBUG:  checkpoint record is at
> E/3B785168
> 2002-07-29 13:37:46 [22138]  DEBUG:  redo record is at
> E/3B785168; undo
> record is at 0/0; shutdown TRUE
> 2002-07-29 13:37:46 [22138]  DEBUG:  next transaction id: 179915804;
> next oid: 95552489
> 2002-07-29 13:37:46 [22138]  DEBUG:  database system was not properly
> shut down; automatic recovery in progress
> 2002-07-29 13:37:46 [22138]  DEBUG:  ReadRecord: record with
> zero length
> at E/3B7851A8
> 2002-07-29 13:37:46 [22138]  DEBUG:  redo is not required
> 2002-07-29 13:37:48 [22138]  DEBUG:  database system is ready
>
> Any ideas?
>
> Regards,
>
>     Markus
>
>