From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Casey Lyon <casey(at)earthcars(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Thanks, naming conventions, and count() |
Date: | 2001-05-02 09:58:38 |
Message-ID: | 3AEFDA4E.B1D6E9F2@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> > 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.
why not have just one ever-growing file that is only appended to and
that has
lines of form
OID, type (DB/TABLE/INDEX/...), name, time
so when you need tha actual info you grep for name and use tha last line
whose
file actually exists. Not too convenient but useful enough when you
really need it.
-------------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Samuel | 2001-05-02 11:28:11 | Re: Thanks, naming conventions, and count() |
Previous Message | Hannu Krosing | 2001-05-02 09:27:02 | Re: v7.1 error ... SELECT converted to a COPY? |