Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id f7ODdkP53718
	for <pgsql-admin@postgresql.org>; Fri, 24 Aug 2001 09:39:46 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f7ODddK02959;
	Fri, 24 Aug 2001 09:39:40 -0400 (EDT)
To: mark@vestnesis.lv
cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM problems 
In-reply-to: <3B864390.1648.FC72935@localhost> 
References: <3B864390.1648.FC72935@localhost>
Comments: In-reply-to "Martins Zarins" <mark@vestnesis.lv>
	message dated "Fri, 24 Aug 2001 12:07:44 +0300"
Date: Fri, 24 Aug 2001 09:39:39 -0400
Message-ID: <2956.998660379@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200108/105
X-Sequence-Number: 2041

"Martins Zarins" <mark@vestnesis.lv> writes:
> Some rows are up to 400Kb lenght. The database is 
> working just fine, but vacuum crashes all the time after procesing 
> that full text table.

You're going to have to provide more information than that.  What
happens *exactly*?  What shows up in the postmaster's stderr log?
Is there a core file, and if so can you get a backtrace from it?

			regards, tom lane