| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Jim Nasby <decibel(at)decibel(dot)org> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, 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-28 08:08:34 |
| Message-ID: | 46330102.6010007@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Jim Nasby wrote:
> On Apr 27, 2007, at 12:35 PM, Gregory Stark wrote:
>> 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?
Well, yes, except that it will bloat the table. If you wanted to
physically drop the column to save space, you're not going to be happy
with that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lexington Luthor | 2007-04-28 08:19:54 | Re: Processing a work queue |
| Previous Message | Listmail | 2007-04-28 07:13:22 | Re: Query in function not using index... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cui Shijun | 2007-04-28 09:25:18 | Re: Fwd: How does the partitioned lock manager works? |
| Previous Message | Heikki Linnakangas | 2007-04-28 08:06:25 | Re: Fwd: How does the partitioned lock manager works? |