Am experimenting to find out what kind of performance gain are achieved
from moving indexes to a different scsi drives than the WAL files, than
the data itself, etc.
Have come across an interesting problem.
Have moved the indexes to another drive, then created symlinks to them.
Ran a benchmark against the database, REINDEX'd the tables, VACUUM FULL
ANALYZE'd, prepared to re-run the benchmark again and guess what?
The indexes were back on the original drive.
The process of REINDEX-ing obviously creates another file then drops the
Is there a way to allow REINDEX to work without having this side affect?
Pre-creating a bunch of dangling symlinks doesn't work (tried that, it
gives a "ERROR: cannot create accounts_pkey: File exists" on FreeBSD
4.6.2 when using the REINDEX).
Regards and best wishes,
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
pgsql-hackers by date
|Next:||From: Shridhar Daithankar||Date: 2002-09-28 07:16:04|
|Subject: Re: How to REINDEX in high volume environments?|
|Previous:||From: Neil Conway||Date: 2002-09-28 05:30:45|
|Subject: Re: making use of large TLB pages|