| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "rupesh bajaj" <rupesh(dot)bajaj(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: When the locially dropped column is also physically dropped |
| Date: | 2007-04-27 17:41:34 |
| Message-ID: | 77FF7F8C-6BF0-44F7-84EE-6DE3D26EF12C@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general 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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Harris | 2007-04-27 17:47:48 | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Previous Message | Tom Lane | 2007-04-27 17:18:38 | Re: Processing a work queue |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2007-04-27 17:43:54 | Re: Hi, I wanto joinin the developer group of postgresql |
| Previous Message | Jim Nasby | 2007-04-27 17:33:06 | Re: too much WAL volume |