RE: [HACKERS] Re: ALTER TABLE DROP COLUMN
Hiroshi Inoue <inoue@tpf.co.jp>
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Bruce Momjian" <pgman@candle.pha.pa.us>, "The Hermit Hacker" <scrappy@hub.org>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "PostgreSQL Development" <pgsql-hackers@postgreSQL.org>
Date: 2000-02-28T07:16:43Z
Lists: pgsql-hackers
> -----Original Message----- > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] > > > > I would also change attname to '*already dropped %d' for > > > examle to avoid duplicate attname. > > > > Okay, just curious here, but ... what you are proposing *sounds* to me > > like half-way to what started this thread. (*Please* correct me if I'm > > wrong) ... > > > > Essentially, in your proposal, when you drop a column, all subsequent > > tuples inserted/updated would have ... that one column missing? So, > > instead of doing a massive sweep through the table and removing that > > column, only do it when an insert/update happens? > > > > Basically, eliminate the requirement to re-write every tuples, > only those > > that have activity? > > And I think the problem was that there was too much code to modify to > allow this. > Seems my trial would be useless. I would give up the trial. Regards. Hiroshi Inoue Inoue@tpf.co.jp