diff --git a/doc/src/sgml/ref/alter_foreign_table.sgml b/doc/src/sgml/ref/alter_foreign_table.sgml
index 9d14b19..c2ebdac 100644
*** a/doc/src/sgml/ref/alter_foreign_table.sgml
--- b/doc/src/sgml/ref/alter_foreign_table.sgml
***************
*** 264,270 **** ALTER FOREIGN TABLE name
added or removed with ADD COLUMN or
DROP COLUMN, a system oid> column is added
or removed, a CHECK> or NOT NULL> constraint is
! added, or column type is changed with ALTER TYPE>. It is the
user's responsibility to ensure that the table definition matches the
remote side.
--- 264,270 ----
added or removed with ADD COLUMN or
DROP COLUMN, a system oid> column is added
or removed, a CHECK> or NOT NULL> constraint is
! added, or column type is changed with SET DATA TYPE>. It is the
user's responsibility to ensure that the table definition matches the
remote side.
diff --git a/doc/src/sgml/ref/alter_table.sgml bindex 17a1d34..5c94a9f 100644
*** a/doc/src/sgml/ref/alter_table.sgml
--- b/doc/src/sgml/ref/alter_table.sgml
***************
*** 719,725 **** ALTER TABLE name
! The fact that ALTER TYPE> requires rewriting the whole table
is sometimes an advantage, because the rewriting process eliminates
any dead space in the table. For example, to reclaim the space occupied
by a dropped column immediately, the fastest way is:
--- 719,725 ----
! The fact that SET DATA TYPE> requires rewriting the whole table
is sometimes an advantage, because the rewriting process eliminates
any dead space in the table. For example, to reclaim the space occupied
by a dropped column immediately, the fastest way is:
***************
*** 734,748 **** ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
! The USING option of ALTER TYPE> can actually
specify any expression involving the old values of the row; that is, it
can refer to other columns as well as the one being converted. This allows
! very general conversions to be done with the ALTER TYPE>
syntax. Because of this flexibility, the USING
expression is not applied to the column's default value (if any); the
result might not be a constant expression as required for a default.
This means that when there is no implicit or assignment cast from old to
! new type, ALTER TYPE> might fail to convert the default even
though a USING clause is supplied. In such cases,
drop the default with DROP DEFAULT>, perform the ALTER
TYPE>, and then use SET DEFAULT> to add a suitable new
--- 734,748 ----
! The USING option of SET DATA TYPE> can actually
specify any expression involving the old values of the row; that is, it
can refer to other columns as well as the one being converted. This allows
! very general conversions to be done with the SET DATA TYPE>
syntax. Because of this flexibility, the USING
expression is not applied to the column's default value (if any); the
result might not be a constant expression as required for a default.
This means that when there is no implicit or assignment cast from old to
! new type, SET DATA TYPE> might fail to convert the default even
though a USING clause is supplied. In such cases,
drop the default with DROP DEFAULT>, perform the ALTER
TYPE>, and then use SET DEFAULT> to add a suitable new