Corrections to ALTER FOREIGN TABLE documentation.

Shigeru Hanada, with a minor grammar correction.

diff --git a/doc/src/sgml/ref/alter_foreign_table.sgml b/doc/src/sgml/ref/alter_foreign_table.sgml
index c2ebdac8479a5355de9e96b79dd2763b600041c7..a45df020ea143f099719de827410190a5176564d 100644 (file)
--- a/doc/src/sgml/ref/alter_foreign_table.sgml
+++ b/doc/src/sgml/ref/alter_foreign_table.sgml
@@ -32,7 +32,7 @@ ALTER FOREIGN TABLE name
 
 where action is one of:
 
-    ADD [ COLUMN ] column type
+    ADD [ COLUMN ] column type [ NULL | NOT NULL ]
     DROP [ COLUMN ] [ IF EXISTS ] column [ RESTRICT | CASCADE ]
     ALTER [ COLUMN ] column [ SET DATA ] TYPE type
     ALTER [ COLUMN ] column { SET | DROP } NOT NULL
@@ -125,7 +125,7 @@ ALTER FOREIGN TABLE name
     OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
     
      
-      Change options for the foreign table or the column of the foreign table.
+      Change options for the foreign table.
       ADD, SET, and DROP
       specify the action to be performed.  ADD is assumed
       if no operation is explicitly specified.  Option names must be
@@ -150,8 +150,6 @@ ALTER FOREIGN TABLE name
    You must own the table to use ALTER FOREIGN TABLE.
    To change the schema of a foreign table, you must also have
    CREATE privilege on the new schema.
-   To add the table as a new child of a parent table, you must own the
-   parent table as well.
    To alter the owner, you must also be a direct or indirect member of the new
    owning role, and that role must have CREATE privilege on
    the table's schema.  (These restrictions enforce that altering the owner
@@ -260,12 +258,11 @@ ALTER FOREIGN TABLE name
    
 
    
-    Consistency with the foreign server is not checked when a column is
-    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
+    Consistency with the foreign server is not checked when a column is added
+    or removed with ADD COLUMN or
+    DROP COLUMN, a NOT NULL constraint is
+    added, or a column type is changed with SET DATA TYPE.  It is
+    the user's responsibility to ensure that the table definition matches the
     remote side.