Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: When the locially dropped column is also physically dropped
- 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: Sat, 28 Apr 2007 09:08:34 +0100
- Message-id: <46330102.6010007@enterprisedb.com> <text/plain>
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 TYPEtype" 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
- References:
- When the locially dropped column is also physically dropped
- From: rupesh bajaj
- Re: When the locially dropped column is also physically dropped
- From: Gregory Stark
- Re: When the locially dropped column is also physically dropped
- From: Jim Nasby
- When the locially dropped column is also physically dropped
- Prev by Date: Re: Fwd: How does the partitioned lock manager works?
- Next by Date: Re: Fwd: How does the partitioned lock manager works?
- Previous by thread: Re: When the locially dropped column is also physically dropped
- Next by thread: MSVC
- Indexes: