Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE
От | Robert Haas |
---|---|
Тема | Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE |
Дата | |
Msg-id | AANLkTinD26aEHv8p5O3yZ1YBAL9NgpaTRkVR=rEcd0L=@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP
ATTRIBUTE
|
Список | pgsql-hackers |
On Wed, Mar 30, 2011 at 9:30 PM, Noah Misch <noah@leadboat.com> wrote: >> Perhaps it would be reasonable to extend ALTER TABLE .. [NO] >> INHERIT to accept a type name as the final argument. If used in this >> way, it converts a typed table into a regular table or visca versa. > > Why extend ALTER TABLE ... INHERIT? I would have guessed independent syntax. I just didn't feel the need to invent something new, but we could if someone would rather. >> We could also do it with a direct catalog change, but there are some >> dependencies that would need to be frobbed, which makes me a bit >> reluctant to go that way. > > Agreed; it's also an independently-useful capability to have. Yep. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: