Re: When the locially dropped column is also physically dropped - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: When the locially dropped column is also physically dropped
Date
Msg-id 77FF7F8C-6BF0-44F7-84EE-6DE3D26EF12C@decibel.org
Whole thread Raw
In response to Re: When the locially dropped column is also physically dropped  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: When the locially dropped column is also physically dropped  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
On Apr 27, 2007, at 12:35 PM, Gregory Stark wrote:
>> I have dropped a column (say column name is 'A') from the relation  
>> R. By
>> setting the attisdropped as true in the pg_catalog.pg_attribute  
>> table. But
>> the column is dropped locially not the physically. Can you please  
>> tell me
>> when this column will be physically also dropped. Is this column is
>> automatically physically dropped? or I have to run some command to  
>> dropped
>> it physically.
>
> These kinds of questions are best sent to pgsql-general instead of - 
> hackers.
>
> The column won't be dropped physically until you execute one of the  
> commands
> that rewrites the table entirely. "CLUSTER" and "ALTER TABLE ALTER  
> column TYPE
> type" are the two popular ones.

UPDATE SET field1 = field1; would also work, right?
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: too much WAL volume
Next
From: Jim Nasby
Date:
Subject: Re: Hi, I wanto joinin the developer group of postgresql