Skip site navigation (1) Skip section navigation (2)

Re: Composite types as columns used in production?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Robinson <jlrobins(at)socialserve(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Composite types as columns used in production?
Date: 2005-04-29 16:21:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
James Robinson <jlrobins(at)socialserve(dot)com> writes:
> 	Hmm -- I see that if the composite type was created via a table 
> definition, then you _can_ actually add and drop columns, and the 
> tables using the composite type seem to get updated, as in 
> . 
> That's sweet, and if this is supportable functionality as opposed to an 
> odd side-effect, then the 'ALTER TYPE' and 'CREATE TYPE' doc pages may 
> well want to reference this feature.

My recollection is that there are some pretty serious limitations on
what you can do in this line, but basic cases do work.  I think the lack
of an ALTER TYPE that can handle the same cases is just a matter of lack
of round tuits.

			regards, tom lane

In response to


pgsql-general by date

Next:From: KeatisDate: 2005-04-29 16:34:56
Subject: Re: Problem: message type 0xxx arrived from server while idle
Previous:From: Tom LaneDate: 2005-04-29 16:15:38
Subject: Re: Increasing statistics results in worse estimates

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group