From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Applying TOAST to CURRENT |
Date: | 2000-05-30 16:20:44 |
Message-ID: | 200005301620.MAA12712@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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.
>
> If you want to control it with an ALTER TABLE function, let's add ALTER
> TABLE DROP TOAST so that admins who don't like the excess space usage
> can get rid of it. (Of course that should only succeed after verifying
> the toast table is empty...)
But when you vacuum a table, doesn't it get zero size? Sure works here:
#$ cd /u/pg/data/base/test
#$ ls -l kkk*
-rw------- 1 postgres postgres 0 May 30 12:20 kkk
#$
--
Bruce Momjian | http://www.op.net/~candle
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-30 16:33:21 | CVS log of only one branch |
Previous Message | The Hermit Hacker | 2000-05-30 16:11:21 | Re: Applying TOAST to CURRENT |