Re: Allowing ALTER TYPE to change storage strategy
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2020-03-06T17:20:43Z
Lists: pgsql-hackers
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes: > On Thu, Mar 05, 2020 at 05:46:44PM -0500, Tom Lane wrote: >> For ease of review I just added the new TCFLAGS value out of >> sequence, but I'd be inclined to renumber the bits back into >> sequence before committing. > LGTM. If I had to nitpick, I'd say that the example in docs should be > ALTER TYPE mytype SET ( > SEND = mytypesend, > RECEIVE = mytyperecv > ); > i.e. with uppercase SEND/RECEIVE, because that's how we spell it in > other examples in CREATE TYPE etc. OK, pushed with those changes and some other docs-polishing. regards, tom lane
Commits
-
Allow ALTER TYPE to change some properties of a base type.
- fe30e7ebfa38 13.0 landed