From: Martins Zarins <mark@vestnesis.lv>
To: pgsql-admin@postgresql.org
Subject: VACUUM problems
Date: Fri, 24 Aug 2001 12:07:44 +0300
Message-ID: <3B864390.1648.FC72935@localhost> (raw)
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
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-admin@postgresql.org
Cc: mark@vestnesis.lv
Subject: Re: VACUUM problems
In-Reply-To: <3B864390.1648.FC72935@localhost>
* 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