| From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | "The Hermit Hacker" <scrappy(at)hub(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | RE: [HACKERS] Well, then you keep your darn columns |
| Date: | 2000-01-25 02:05:35 |
| Message-ID: | 001101bf66d8$aad4b8e0$2801007e@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: The Hermit Hacker [mailto:scrappy(at)hub(dot)org]
>
> > 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 ...
>
AFAIK,there's no such logic in VACUUM.
Because PostgreSQL has no rollback data separately,we must keep
valid old tuples somewhere(of cource the original place is most natural)
in the table until commit at least.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2000-01-25 02:06:35 | Re: [HACKERS] fatal copy in/out error (6.5.3) |
| Previous Message | Hiroshi Inoue | 2000-01-25 01:58:43 | RE: [HACKERS] Happy column dropping |