Excerpts from rikard.pavelic's message of sáb feb 25 10:23:18 -0300 2012:
> But I would expect second alter to pass and enforcing not null and default
> when adding this column in table and not enforcing not null and default when
> adding into composite type for another table.
> Is this by design, oversight or a TODO?
I think this is more a TODO than anything else. Last year we discussed
something similar to this -- twice, even; IIRC, one was buried somewhere
in the discussion about "variant" types, if you want to search the
pgsql-hackers archives. As far as I recall, discussion died mainly
because no one had the time and/or energy to pursue it, not because it
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2012-02-29 16:02:56|
|Subject: Re: BUG #6494: Listening to * fails for IP V6 |
|Previous:||From: Curd Reinert||Date: 2012-02-29 09:57:56|
|Subject: Re: BUG #6494: Listening to * fails for IP V6|