Changes we are considering would result in a large number of aliases,
quite possibly exceeding 100,000.

I'd appreciate anyone's experience or knowledge as to whether this is
better done as one big aliases file or as several files.

Joseph Brennan
Academic Technologies Group, Academic Information Systems (AcIS)
Columbia University in the City of New York

Joseph Brennan wrote:
> Changes we are considering would result in a large number of aliases,
> quite possibly exceeding 100,000.
>
> I'd appreciate anyone's experience or knowledge as to whether this is
> better done as one big aliases file or as several files.

You may consider keeping aliases in btree database and using "sorted" alias
file used to build the database *WHEN* newaliases command takes too long.

Using btree database build from key sorted input file reduces time required to
build/rebuild the database.

--
Andrzej [en:Andrew] Adam Filip anfi [at] priv.onet.pl anfi [at] xl.wp.pl
Home Page http://anfi.homeunix.net/ [ PageRank 6 ]
*Random Epigram* :
A lizard on a cushion will still seek leaves.
-- Russian Proverb