Postgres Pro
Downloads
Home   >   mailing lists

Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine
Date
Msg-id b42b73150812080453x13276086n7a662cf04b3b4259@mail.gmail.com
Whole thread Raw
In response to Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine  ("Robert Haas" <robertmhaas@gmail.com>)
Responses Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine  (Andrew Dunstan <andrew@dunslane.net>)
Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine  ("Robert Haas" <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On Sun, Dec 7, 2008 at 10:17 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sun, Dec 7, 2008 at 7:57 PM, Bruce Momjian <bruce@momjian.us> wrote:
>> Dmitry Koterov wrote:
>>> Could you please say, if ALTER TYPE ... ADD COLUMN is planned for a future
>>> PostgreSQL version?
>>
>> It is not currently on the TODO list.
>
> Perhaps we could add it?  It's been complained about more than once in
> this space.

Well, new features that have a perfectly acceptable and usable
workaround typically have a fairly low priority of fixing :-)

Since tables are basically types, I'm not sure what the difference is
between tables and composite types (meaning, why do we have the
composite type syntax at all?)  I'm not sure if this came up during
the design discussion or not.

merlin

pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: new vacuum is slower for small tables
Next
From: "Pavan Deolasee"
Date:
Subject: Re: visibility maps and heap_prune