Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Date: 2011-03-31T01:37:56Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix pg_dump to handle collations applied to columns of composite types.
- acfa1f45ed3e 9.1.0 cited
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