dblink_open(text cursorname, text sql [, bool fail_on_error]) returns text dblink_open(text connname, text cursorname, text sql [, bool fail_on_error]) returns text
dblink_open() opens a cursor in
a remote database. The cursor can subsequently be manipulated
Name of the connection to use; omit this parameter to use the unnamed connection.
The name to assign to this cursor.
The SELECT statement that you wish to execute in the remote database, for example select * from pg_class.
If true (the default when omitted) then an error thrown on the remote side of the connection causes an error to also be thrown locally. If false, the remote error is locally reported as a NOTICE, and the function's return value is set to ERROR.
Since a cursor can only persist within a transaction,
dblink_open starts an explicit
transaction block (BEGIN) on the remote
side, if the remote side was not already within a transaction.
This transaction will be closed again when the matching
dblink_close is executed. Note that
if you use
dblink_exec to change
dblink_close, and then an error
occurs or you use
dblink_close, your change
will be lost because
the transaction will be aborted.
SELECT dblink_connect('dbname=postgres'); dblink_connect ---------------- OK (1 row) SELECT dblink_open('foo', 'select proname, prosrc from pg_proc'); dblink_open ------------- OK (1 row)
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.