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: 6571.1114791703@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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
> http://archives.postgresql.org/pgsql-hackers/2005-03/msg00621.php .
> 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

Responses

Browse pgsql-general by date

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