From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, Szymon Guz <mabewlun(at)gmail(dot)com>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, AI Rumman <rummandba(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: VACUUM FULL for performance |
Date: | 2010-10-07 14:21:53 |
Message-ID: | 28402.1286461313@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Leonardo Francalanci <m_lists(at)yahoo(dot)it> writes:
>> I also recommend reindexing any table that has been VACUUM FULLed.
> Mmmh, from the docs I get that in 9.0 a "vacuum full" rewrites the whole table,
> so I expect the indexes to be re-created anyway... so a reindexing would
> be totally useless.
Any discussion of VACUUM FULL has to recognize that 9.0's implementation
of it is completely different from all prior versions. It still has
disadvantages, but not the ones that were there before.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-07 14:26:50 | Re: pg_relation_size / could not open relation with OID # |
Previous Message | Tom Lane | 2010-10-07 14:17:42 | Re: PostgreSQL 7.4.16 is creating strange files under /var/lib/pgsql |