| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "onion" <onion(at)taxi(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Vacuum writes on empty system |
| Date: | 2004-10-01 18:33:47 |
| Message-ID: | 13342.1096655627@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"onion" <onion(at)taxi(dot)com> writes:
> I just loaded up 9GB of data (32 tables) into a brand new system (Postgres
> 7.4.5 on Linux 2.4 with 1GB ram, IDE). I immediately ran "vacuum analyze"
> but Postgres seems to be writing a lot to disk even though none of the
> tables have incurred any UPDATES or DELETES yet and there are no other
> connections or process running. Is it normal for vacuum to be writing to
> disk even when there is nothing to clean up?
Your assumption that there is nothing for VACUUM to do is mistaken.
It's probably setting the known-committed hint bits in all the tuple
headers of the newly loaded data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2004-10-01 18:44:37 | Re: date_trunc'd timestamp index possible? |
| Previous Message | D. Duccini | 2004-10-01 18:28:47 | Re: date_trunc'd timestamp index possible? |