Re: When the locially dropped column is also physically dropped - Mailing list pgsql-general

From Tom Lane
Subject Re: When the locially dropped column is also physically dropped
Date
Msg-id 9088.1177968607@sss.pgh.pa.us
Whole thread Raw
In response to Re: When the locially dropped column is also physically dropped  (Chris Browne <cbbrowne@acm.org>)
List pgsql-general
Chris Browne <cbbrowne@acm.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: NFS vs. PostgreSQL on Solaris
Next
From: Michael Glaesemann
Date:
Subject: Re: pgsql and Mac OS X