Here is what I suggested for oid2name to do with file names:
---------------------------------------------------------------------------
Just seems like a major pain; not worth the work.
If you do a ls and pipe it, here is what you would need to do:
- find out where $PWD is
- in that database (found from PID), for each file in the dir, look it
up using oid2name
- print that out
problems:
- ls -l vs ls
- column are different for differing OSs / filesystems
- du will REALLY suck
- what if the user tries to do "ls /var/postgres/data/base/12364" Will
you try to parse out the request? Ugh. no thanks.
I also don't think people will have much reason to use the script.
oid2name will have little enough use, what use will the script have? Who
knows.. I guess keep it on back burner till there is a demand.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
