The dblink module supports connections to other Greenplum Database databases from within a database session. These databases can reside in the same Greenplum Database system, or in a remote system.
Greenplum Database supports dblink connections between databases in Greenplum Database installations with the same major version number. dblink may also connect to other Greenplum Database installations that use compatible libpq libraries.
You create a dblink connection to a database and execute an SQL command in the database as a Greenplum Database user. The user must have the appropriate access privileges to the database tables referenced in the SQL command. If the database is in a remote system, the user must be defined as a Greenplum Database user in the remote system with the appropriate access privileges.
dblink is intended for database users to perform short ad hoc queries in other databases. dblink is not intended for use as a replacement for external tables or for administrative tools such as gpcopy or gptransfer.
Refer to dblink in the PostgreSQL documentation for more information about individual dblink functions.
gpadmin=# CREATE TABLE testdbllocal (a int, b text) DISTRIBUTED BY (a); CREATE TABLE gpadmin=# INSERT INTO testdbllocal select * FROM dblink('dbname=postgres', 'SELECT * FROM testdblink') AS dbltab(id int, product text); INSERT 0 2
The following procedure identifies the basic steps for configuring and using dblink in Greenplum Database. The examples use dblink_connect() to create a connection to a database and dblink() to execute an SQL query.
Only superusers can use dblink_connect() to create connections that do not require a password. If non-superusers need this capability, use dblink_connect_u() instead. See Using dblink as a Non-Superuser.
- Begin by creating a sample table to query using the dblink functions.
These commands create a small table in the postgres database, which you
will later query from the testdb database using
$ psql -d postgres psql (8.3.23) Type "help" for help. postgres=# CREATE TABLE testdblink (a int, b text) DISTRIBUTED BY (a); CREATE TABLE postgres=# INSERT INTO testdblink VALUES (1, 'Cheese'), (2, 'Fish'); INSERT 0 2 postgres=# \q $
- Log into a different database as a superuser. In this example, the superuser
gpadmin logs into the database testdb. If the
dblink functions are not already available, install them using the
$ psql -d testdb psql (9.4beta1) Type "help" for help. testdb=# \i /usr/local/greenplum-db/share/postgresql/contrib/dblink.sql SET CREATE FUNCTION CREATE FUNCTION ...
- Use the dblink_connect() function to create either an implicit or a
named connection to another database. The connection string that you provide should be a
libpq-style keyword/value string. This example creates a connection named
mylocalconn to the postgres database on the local
Greenplum Database system:
testdb=# SELECT dblink_connect('mylocalconn', 'dbname=postgres user=gpadmin'); dblink_connect ---------------- OK (1 row)Note: If a user is not specified, dblink_connect() uses the value of the PGUSER environment variable when Greenplum Database was started. If PGUSER is not set, the default is the system user that started Greenplum Database.
- Use the dblink() function to query a database using a configured
connection. Keep in mind that this function returns a record type, so you must assign the
columns returned in the dblink() query. For example, the following
command uses the named connection to query the table you created
testdb=# SELECT * FROM dblink('mylocalconn', 'SELECT * FROM testdblink') AS dbltab(id int, product text); id | product ----+--------- 1 | Cheese 2 | Fish (2 rows)
To connect to the local database as another user, specify the user in the connection string. This example connects to the database as the user test_user. Using dblink_connect(), a superuser can create a connection to another local database without specifying a password.
testdb=# SELECT dblink_connect('localconn2', 'dbname=postgres user=test_user');
testdb=# SELECT dblink_connect('host=remotehost port=5432 dbname=postgres user=gpadmin password=secret');