Re: When the locially dropped column is also physically dropped
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: "rupesh bajaj" <rupesh(dot)bajaj(at)gmail(dot)com>
- Cc: <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: When the locially dropped column is also physically dropped
- Date: Fri, 27 Apr 2007 12:35:26 +0100
- Message-id: <87lkgejbi9.fsf@oxford.xeocode.com> <text/plain>
"rupesh bajaj" <rupesh(dot)bajaj(at)gmail(dot)com> writes:
> Hi,
> 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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Home |
Main Index |
Thread Index