I don't know if this would work, but if you just want to restructure your
rows, your could do this:
UPDATE table SET id = id WHERE id BETWEEN 0 AND 2;
VACUUM table;
UPDATE table SET id = id WHERE id BETWEEN 20001 AND 4;
VACUUM table;
wash, rinse,
<[EMAIL PROTECTED]>
(BCc: "Michael Ryan S. Puncia" <[EMAIL PROTECTED]>;
(B
(BSent: Tuesday, February 15, 2005 2:30 PM
(BSubject: Re: [PERFORM] VACCUM FULL ANALYZE PROBLEM
(B
(B
(B> "Iain" <[EMAIL PROTECTED]> writes:
(B>>> another way to spe
"Iain" <[EMAIL PROTECTED]> writes:
>> another way to speed up full vacuum?
> Hmmm... a full vacuum may help to re-organize the structure of modified
> tables, but whether this is significant or not is another matter.
Actually, VACUUM FULL is designed to work nicely for the situation where
a ta
inal Message -
From:
Michael
Ryan S. Puncia
To: 'Iain' ; pgsql-performance@postgresql.org
Sent: Tuesday, February 15, 2005
11:10 AM
Subject: RE: [PERFORM] VACCUM FULL
ANALYZE PROBLEM
But I need to do full
vacuum because I deleted some of the
On Tue, 2005-02-15 at 09:34 +0800, Michael Ryan S. Puncia wrote:
> Hi,
>
>
>
> I have 3 tables in the database with 80G of data, one of them is
> almost 40G and the remaining 2 tables has 20G each.
>
> We use this database mainly for query and updating is done only
> quarterly and the database
Hi,
just make sure that your freespace map is
big enough and then do a vacuum analyse without the full option.
I can imagine that database performance
might not be as good as it would be after a vacuum full, though I expect that it
wouldn't make much difference.
regards
Iain
-
. Puncia; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] VACCUM FULL
ANALYZE PROBLEM
Hi,
just make sure that your freespace map is
big enough and then do a vacuum analyse without the full option.
I can imagine that database performance
might not be as good as it
