From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Applying TOAST to CURRENT |
Date: | 2000-05-30 20:22:06 |
Message-ID: | 393422EE.8CD59BC3@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> On Tue, 30 May 2000, Hannu Krosing wrote:
>
> > The only drawback is bloating directories, but it was already suggested
> > that
> > TOAST tables could/should be kept in subdirectory toast (as should
> > indexes
> > too, imho).
>
> still say, simplest "fix":
>
> <dbname>/{system,db,toast,index}
Why can't we just add a column named "tablepath" to pg_table, that can
either be
a simple filename, or relative path with a filename or even full path
(if we don't worry too much for security ;)
That has came up before when discussing ways to make rename table
rollbackable
but it could be handy here two.
AFAIK it has been a general principle in programming to keep separate
things
separate unless a very good reason not to do so is present.
-----------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-30 20:24:52 | Does pg_passwd files work with crypt |
Previous Message | Bruce Momjian | 2000-05-30 20:13:03 | config files in /data |