Horton

Re: Big 7.1 open items

Bruce Momjian <pgman@candle.pha.pa.us>

View thread
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hiroshi Inoue <Inoue@tpf.co.jp>, Peter Eisentraut <peter_e@gmx.net>, Jan Wieck <JanWieck@Yahoo.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, "Ross J. Reedstrom" <reedstrm@rice.edu>
Date: 2000-06-21T17:05:39Z
Lists: pgsql-hackers 
> > Just seems easier to have stuff segregates into separate per-db
> > directories for clarity.  Also, as directories get bigger, finding a
> > specific file in there becomes harder.  Putting 10 databases all in the
> > same directory seems bad in this regard.
> 
> Huh?  I wasn't arguing against making a db-specific directory below the
> tablespace point.  I was arguing against making *another* directory
> below that one.

I was suggesting:

	ln -s /var/pgsql/dbname/loc data/base/dbname/loc

I thought you were suggesting:

	ln -s /var/pgsql/dbname data/base/dbname/loc

With this system:

	ln -s /var/pgsql/dbname data/base/dbname/loc1
	ln -s /var/pgsql/dbname data/base/dbname/loc2

go into the same directory, which makes it impossible to move loc1
easily using the file system.  Seems cheap to add the extra directory.

> > I don't think we want to be using
> > symlinks for tables if we can avoid it.
> 
> Agreed, but where did that come from?  None of these proposals mentioned
> symlinks for anything but directories, AFAIR.

I thought you mentioned it.  Sorry.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026