From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Dmitry Samersoff <dms(at)wplus(dot)net> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Index recreation in vacuum |
Date: | 2000-01-19 21:32:25 |
Message-ID: | 200001192132.QAA26048@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I heard from someone that old vacuum had been like so.
> > Probably 2x disk space for big tables was a big disadvantage.
>
> Yes, It is critical.
>
> How about sequence like this:
>
> * Drop indices (keeping somewhere index descriptions)
> * vacuuming table
> * recreate indices
>
> If something crash, user have been noticed
> to re-run vacuum or recreate indices by hand
> when system restarts.
>
> I use script like described above for vacuuming
> - it really increase vacuum performance for large table.
We need two things:
auto-create index on startup
allow vacuum to run only if number of tuples superceeded > X %
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Samersoff | 2000-01-19 21:41:26 | Re: [HACKERS] Index recreation in vacuum |
Previous Message | Dmitry Samersoff | 2000-01-19 21:29:01 | Re: [HACKERS] Index recreation in vacuum |