| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Well, then you keep your darn columns |
| Date: | 2000-01-26 00:56:12 |
| Message-ID: | 388E462C.D7DCAC4D@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> > numbered. How does a missing attribute get handled for new rows?
> > My guess is that we have to keep this thing around forever. Can you
> > imagine having all those user apps tha query pg_attribute supress that
> > column. Sound like too much work to me.
>
> I *still* think the best is the "re-write the table in place" method
> ... we already have most of the logic, I would think, from VACUUM ...
It is much safer with vacuum, as there is no way for vacuum to crash and have
two different tuple formats left behind (i hope ;-p)
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-01-26 01:05:11 | Re: [HACKERS] --enable-debug |
| Previous Message | Oliver Elphick | 2000-01-26 00:45:20 | Re: [HACKERS] Column ADDing issues |