Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink) - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink)
Date
Msg-id 388520E3.D192ED7B@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink)
Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink)
List pgsql-hackers
> > > Yes, that's about the sum of it.  Why not the links?  I think
> > > that it's an elegant way of designing the whole thing.
> > The only problem with symlinks is, that it does not solve the
> > "too many files in one directory to give optimal performance"
> > problem for those that have tons of tables.
> Is that really a problem on modern operating systems?  We could actually
> hash the file names into directory buckets and access them that way, and
> have one directory that old symlinks to the hashed files.

imho symlinks is exactly the wrong way to head on this. If the system
needs to know the true location of something, then it may as well
refer to that location explicitly. Our storage manager should learn
how to deal with explicit locations, and we shouldn't implement this
just as a patch on the table creation code.

My $.02...
                  - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] Index recreation in vacuum
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [hackers]development suggestion needed (filepath as symlink)