> Could one run a postgresql process in a lower priority process and
> perform lazy vacuums without affecting performance all that much?
One must be very careful not to introduce reverse priority problems -
lower priority process locking some resource and then not letting go
higher priority processes are blocked from running due to needing that
In my tests 1 vacuum process slowed down 100 concurrent pgbench
by ~2 times.
> A live index compaction can be done by indexing the table with a
> temporary name rename the old index, rename the new index to the old
> name, and drop the old index.
Isn't this what REINDEX command does ?
In response to
pgsql-hackers by date
|Next:||From: Christopher Kings-Lynne||Date: 2002-01-29 07:42:59|
|Subject: timing queries|
|Previous:||From: Hiroshi Inoue||Date: 2002-01-29 07:18:14|
|Subject: Re: Improving backend launch time by preloading relcache|