Received: from lv-fw ([159.148.47.190])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id f7O9DrP73865
	for <pgsql-admin@postgresql.org>; Fri, 24 Aug 2001 05:13:53 -0400 (EDT)
	(envelope-from mark@vestnesis.lv)
Received: (from mail@localhost) by lv-fw (8.11.1/8.11.1) id f7OAGjL66155
	for pgsql-admin@postgresql.org; Fri, 24 Aug 2001 12:16:45 +0200 (EET)
	(envelope-from mark@vestnesis.lv)
X-Authentication-Warning: lv-fw: mail set sender to mark@vestnesis.lv using -f
Received: from 159.148.47.188 by 216.126.85.28 id EuOfWW90 ;
	24 Aug 2001 12:16:34 EET
Received: from varde (varde [159.148.47.157])
	by vestnesis.lv (8.11.2/x.y.z/Who Cares x.y.z-a.b) with ESMTP id
	f7OABHx24825
	for <pgsql-admin@postgresql.org>; Fri, 24 Aug 2001 12:11:17 +0200
From: "Martins Zarins" <mark@vestnesis.lv>
To: pgsql-admin@postgresql.org
Date: Fri, 24 Aug 2001 12:07:44 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: VACUUM problems
Reply-to: mark@vestnesis.lv
Message-ID: <3B864390.1648.FC72935@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
X-Archive-Number: 200108/103
X-Sequence-Number: 2039

hello, All !

I'm freshman to this list.

Before version 7.1 there was restriction on SQL tuple length 8-32Kb.
Now I'm using 7.1.2 where iz no such limitations. I have created 
some documents database. Theare is table with full text of 
documents. 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. When I deleted all the records from that full text 
table, vacuum did correctly. 
Right now I'm generating the same table but the text is split into 
multiple records each ~8K. I think - it will work.

Maybe that's a bug in vacuum or maybe some misconfiguration (I'm 
using default config).
If anyone had similar problems, pls share your ideas and 
comments about solution.


Mark