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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Chris Browne <cbbrowne(at)acm(dot)org>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: When the locially dropped column is also physically dropped
- Date: Mon, 30 Apr 2007 17:30:07 -0400
Chris Browne <cbbrowne(at)acm(dot)org> writes: > Ron's comment is well-suggested[1], but a bit of a red herring, as the > column will *NEVER* be "physically dropped." [2] Check. > What will happen is that new tuples will not have the column, but old > tuples will continue to have the (invisible) column for as long as > they "live" in the database. Actually, new tuples still have the column, it's just always NULL (and hence takes no space except for a bit in the nulls-bitmap). regards, tom lane
- References:
- When the locially dropped column is also physically dropped
- From: rupesh bajaj
- Re: When the locially dropped column is also physically dropped
- From: Chris Browne
- When the locially dropped column is also physically dropped
- Prev by Date: Re: NFS vs. PostgreSQL on Solaris
- Next by Date: Re: pgsql and Mac OS X
- Previous by thread: Re: When the locially dropped column is also physically dropped
- Next by thread: Preferred Installation/Data Directories
- Indexes: