Re: Thanks, naming conventions, and count()

> I can even think of a situation, as unlikely as it can be, where this
> could happen ... run out of inodes on the file system ... last inode used
> by the table, no inode to stick the symlink onto ...

If you run out of inodes, you are going to have much bigger problems
than symlinks. Sort file creation would fail too.

>
> its a remote situation, but I've personally had it happen ...
>
> I'd personally prefer to see some text file created in the database
> directory itself that contains the mappings ... so that each time there is
> a change, it just redumps that data to the dext file ... less to maintain
> overall ...

Yes, I like that idea, but the problem is that it is hard to update just
one table in the file. You sort of have to update the entire file each
time a table changes. That is why I liked symlinks because they are
per-table, but you are right that the symlink creation could fail
because the new table file was never created or something, leaving the
symlink pointing to nothing. Not sure how to address this. Is there a
way to update a flat file when a single table changes?

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