| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Bitmead <chris(at)bitmead(dot)com> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE DROP COLUMN |
| Date: | 2000-06-12 15:01:01 |
| Message-ID: | 715.960822061@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Chris Bitmead <chris(at)bitmead(dot)com> writes:
> I don't know if this is one of the 5, but my idea of a good
> implementation is to do the fast invisible approach, and then update
> individual tuples to the new format the next time they happen to be
> UPDATEd.
How would you tell whether a particular tuple has been updated or not?
Furthermore, how would you remember the old tuple format (or formats)
so that you'd know how to make the conversion?
Seems to me this approach would require adding some sort of table
version number to every tuple header, plus storing a complete set of
system catalog entries for every past version of each table's schema.
That's a heck of a high price, in both storage and complexity, for a
feature of dubious value...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2000-06-12 15:05:26 | the contrib |
| Previous Message | Tom Lane | 2000-06-12 14:50:46 | Re: Gripe: working on configure now requires Automake installed locally |