Re: Applying TOAST to CURRENT

On Tue, 30 May 2000, Hannu Krosing wrote:

> The Hermit Hacker wrote:
> > 
> > On Tue, 30 May 2000, Tom Lane wrote:
> > >
> > > I agree with Bruce --- the toast table should be created automatically,
> > > at least if the table contains any potentially-toastable columns.  We
> > > want this to be as transparent as possible.  I'd rather have auto create
> > > on-the-fly when first needed, but if that seems too risky then let's
> > > just make the table when its owning table is created.
> > 
> > have to third this one ... I think it should be totally transparent to the
> > admin/user ... just create it when the table is created, what's the worst
> > case scenario?  it never gets used and you waste 16k of disk space?
> 
> You dont even use 16k if toast tables are like ordinary tables (which I 
> guess they are). New empty tables seem to occupy 0k.
> 
> So I'm also for immediate creation of tost tables for all tables that 
> require them, either at create (if there are any toastable columns in 
> the create clause) or at alter table time if first toestable column is 
> added after initial create.
> 
> 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}