| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Kevin Hunter <hunteke(at)earlham(dot)edu> |
| Cc: | Joao Ferreira <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: automatic REINDEX-ing |
| Date: | 2008-08-13 16:53:37 |
| Message-ID: | 20080813165337.GB2958@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 13, 2008 at 12:41:41PM -0400, Kevin Hunter wrote:
> Roughly, VACUUM simply reclaims/frees disk space, while VACUUM FULL
> additionally reorganizes disk usage. I'm still don't know *why* this
> leads to index bloat, however, just that it does. I must defer that
> explication to a Postgres guru.
Because VACUUM FULL needs to move stuff around in the table which means it
need to mess around with the indexes (adding new entries). Ordinary
VACUUM only needs to delete stuff so doesn't cause anywhere near as
many problems.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Ferreira gmail | 2008-08-13 16:58:38 | Re: automatic REINDEX-ing |
| Previous Message | Jeff Ross | 2008-08-13 16:47:17 | Column alias in where clause? |