| From: | "Ian Westmacott" <ianw(at)intellivid(dot)com> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | VACUUM and read-mostly tables |
| Date: | 2005-04-05 03:58:13 |
| Message-ID: | 000201c53993$b07bb440$76d81e42@hsd1.ma.comcast.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I have a near-real-time system writing into a Postgres 7.4.2 database
on the order of 340 million rows per day in about 300 million
transactions. So we quickly bump up against the XID wrap-around
issue. To address this, we divide the tables into 24-hour periods.
Once we roll over to a new period, the old tables are read-mostly.
We then run vacuum every 24 hours.
The problem is that we are writing rows every 1/15 second, 24x7. There
is no down time. I'm wondering if there is any way to avoid vacuuming
the old tables over and over. The documentation seems to indicate that
a full vacuum is needed to avoid XID wrap-around. Can vacuum freeze
help me?
Thanks,
--Ian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-04-05 04:41:28 | Re: VACUUM and read-mostly tables |
| Previous Message | Henric Ernstson | 2005-04-04 21:47:08 | Re: Trying to use initlocation |