use qualified "foreign server" here.
--
Shigeru HANADA
diff --git a/doc/src/sgml/file-fdw.sgml b/doc/src/sgml/file-fdw.sgml
index 889aa77..4acb826 100644
--- a/doc/src/sgml/file-fdw.sgml
+++ b/doc/src/sgml/file-fdw.sgml
@@ -174,7 +174,7 @@ CREATE EXTENSION file_fdw;
- Then cr
I noticed a typo in the description of the column domains.collation_name.
> Name of the collation of the column, null if default ...
This view contains domain entries, so "Name of the collation of the
domain" would be correct.
--
Shigeru HANADA
diff --git a/doc/src/sgml/informatio
ler.html
Please find attached a patch which adds a mention of ALTER and USER MAPPING.
Regards,
--
Shigeru Hanada
diff --git a/doc/src/sgml/fdwhandler.sgml b/doc/src/sgml/fdwhandler.sgml
index c8ae861..c17c540 100644
--- a/doc/src/sgml/fdwhandler.sgml
+++ b/doc/src/sgml/fdwhandler.sgml
@@ -3
(2011/06/17 20:13), Shigeru Hanada wrote:
> I examined the example, and found some points which should be corrected:
>
> - Some lines are over 80 columns.
> - CREATE EXTENSION file_fdw also creates default FOREIGN DATA WRAPPER
> file_fdw, so no need to create FOREIGN DATA WRA
e after
log rotation.
Regards,
--
Shigeru Hanada
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
not committed. On the
other hand, CREATE FOREIGN TABLE document seems fine as is, it doesn't
mention any unsupported feature.
Please find attached a patch for the document correction. The patch
also replaces the phrase "table" with "foreign table" for wording
consisten