> > Can we make some sort of usually-correct-but-not-guaranteed-correct
> > dump that shows which corresponds to what? Maybe something similar
> > to the textfile dump of pg_shadow that the postmaster uses for password
> > authentication? Then at least you'd have some shot at figuring out
> > which file was what in extremis...
>
> As it was proposed - utility to create dir with database name
> (in addition to dir with database oid where data really live)
> and symlinks there: table_name --> ../db_oid/table_oid
That's interesting, but I am concerned about the extra overhead of
creating two links for every file.
The other issue is if the table is accidentally dropped, how do you use
that utility to know the oid of the table that was removed?
I guess I like the OID_tablename idea.
--
Bruce Momjian | http://www.op.net/~candle
maillist@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