Re: Altering a table - positioning new columns - Mailing list pgsql-general

From Manfred Koizar
Subject Re: Altering a table - positioning new columns
Date
Msg-id jt6o2vo2hp54tvuf8eckmfhj1sa93sc9co@4ax.com
Whole thread Raw
In response to Re: Altering a table - positioning new columns  ("Chris Boget" <chris@wild.net>)
List pgsql-general
On Mon, 20 Jan 2003 09:28:50 -0600, "Chris Boget" <chris@wild.net>
wrote:
>I'm curious how difficult this would be to implement...

The current implementation has the benefit that when you add a column
existing tuples don't have to be touched.  Each tuple header stores
the number of attributes (natts) at the time of its creation.  If you
query for an attribute with a higher number, you get NULL.  I don't
think this can be changed easily without breaking lots of things.

Mid-2002 there has been rudimentary discussion about metadata
versioning, but it didn't get beyond its brainstorming phase ...

Servus
 Manfred

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: passwords and 7.3
Next
From: Gregory Seidman
Date:
Subject: Re: passwords and 7.3