Thomas Swan wrote: > >The advantage of symlinks is that an administrator could see how things > >are laid out from the command line. > > > > > > > That's a poor reason to require symlinks. The administrator can just as > easily open up psql and query pg_tablespace to see that same > information. Besides, the postgres doesn't know where to look on the > filesystem for the /path/to/oid without a system catalog lookup. There > doesn't seem to be any sensible reason to force a filesystem requirement > when the core operations are diffferent to begin with. > > If a more global view of all databases is necessary, perhaps there ought > to be a system wide view which could display all of that information at > once: dbname, relation name, and physical location.
Who doesn't have symlinks these days, and is going to be using tablespaces? Even Win32 has them. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
