@@ -777,7 +777,7 @@ ALTER TABLE <replaceable class="PARAMETER">name</replaceable>
777
777
</para>
778
778
779
779
<para>
780
- The fact that <literal>ALTER TYPE</> requires rewriting the whole table
780
+ The fact that <literal>SET DATA TYPE</> requires rewriting the whole table
781
781
is sometimes an advantage, because the rewriting process eliminates
782
782
any dead space in the table. For example, to reclaim the space occupied
783
783
by a dropped column immediately, the fastest way is:
@@ -792,15 +792,15 @@ ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
792
792
</para>
793
793
794
794
<para>
795
- The <literal>USING</literal> option of <literal>ALTER TYPE</> can actually
795
+ The <literal>USING</literal> option of <literal>SET DATA TYPE</> can actually
796
796
specify any expression involving the old values of the row; that is, it
797
797
can refer to other columns as well as the one being converted. This allows
798
- very general conversions to be done with the <literal>ALTER TYPE</>
798
+ very general conversions to be done with the <literal>SET DATA TYPE</>
799
799
syntax. Because of this flexibility, the <literal>USING</literal>
800
800
expression is not applied to the column's default value (if any); the
801
801
result might not be a constant expression as required for a default.
802
802
This means that when there is no implicit or assignment cast from old to
803
- new type, <literal>ALTER TYPE</> might fail to convert the default even
803
+ new type, <literal>SET DATA TYPE</> might fail to convert the default even
804
804
though a <literal>USING</literal> clause is supplied. In such cases,
805
805
drop the default with <literal>DROP DEFAULT</>, perform the <literal>ALTER
806
806
TYPE</>, and then use <literal>SET DEFAULT</> to add a suitable new
0 commit comments