| From: | mlw <markw(at)mohawksoft(dot)com> |
|---|---|
| To: | "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar> |
| Cc: | bpalmer <bpalmer(at)crimelabs(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why vacuum? |
| Date: | 2000-12-14 13:11:25 |
| Message-ID: | 3A38C6FD.3F519E6@mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Martin A. Marques" wrote:
>
> El Mié 13 Dic 2000 16:41, bpalmer escribió:
> > I noticed the other day that one of my pg databases was slow, so I ran
> > vacuum on it, which brought a question to mind: why the need? I looked
> > at my oracle server and we aren't doing anything of the sort (that I can
> > find), so why does pg need it? Any info?
>
> I know nothing about Oracle, but I can tell you that Informix has an update
> statistics, which I don't know if it's similar to vacuum, but....
> What vacuum does is clean the database from rows that were left during
> updates and deletes, non the less, the tables get shrincked, so searches get
> faster.
>
While I would like Postgres to perform statistics, one and a while, on
it own. I like vacuum in general.
I would rather trade unused disk space for performace. The last thing
you need during high loads is the database thinking that it is time to
clean up.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2000-12-14 13:16:20 | Re: Why vacuum? |
| Previous Message | Hannu Krosing | 2000-12-14 13:01:46 | Re: (Updated) Table File Format |