From e93ca1618b92ff4ca3e1ed3bff89179d3e2abd9e Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 31 Jan 2014 17:27:50 -0500 Subject: [PATCH] Add some examples to the postgres_fdw documentation. Michael Paquier --- doc/src/sgml/postgres-fdw.sgml | 62 ++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) diff --git a/doc/src/sgml/postgres-fdw.sgml b/doc/src/sgml/postgres-fdw.sgml index 35924f19f26..e6f6e205815 100644 --- a/doc/src/sgml/postgres-fdw.sgml +++ b/doc/src/sgml/postgres-fdw.sgml @@ -375,6 +375,68 @@ + + Examples + + + Here is an example of creating a foreign table with + postgres_fdw. First install the extension: + + + +CREATE EXTENSION postgres_fdw; + + + + Then create a foreign server using . + In this example we wish to connect to a PostgreSQL server + on host 192.83.123.89 listening on + port 5432. The database to which the connection is made + is named foreign_db on the remote server: + + +CREATE SERVER foreign_server + FOREIGN DATA WRAPPER postgres_fdw + OPTIONS (host '192.83.123.89', port '5432', dbname 'foreign_db'); + + + + + A user mapping, defined with , is + needed as well to identify the role that will be used on the remote + server: + + +CREATE USER MAPPING FOR local_user + SERVER foreign_server + OPTIONS (user 'foreign_user', password 'password'); + + + + + Now it is possible to create a foreign table with + . In this example we + wish to access the table named some_schema.some_table + on the remote server. The local name for it will + be foreign_table: + + +CREATE FOREIGN TABLE foreign_table ( + id serial NOT NULL, + data text +) + SERVER foreign_server + OPTIONS (schema_name 'some_schema', table_name 'some_table'); + + + It's essential that the data types and other properties of the columns + declared in CREATE FOREIGN TABLE match the actual remote table. + Column names must match as well, unless you attach column_name + options to the individual columns to show how they are named in the remote + table. + + + Author -- 2.39.5