PostgreSQL 8.3beta3 Documentation | ||||
---|---|---|---|---|
Prev | Fast Backward | Fast Forward | Next |
dblink_exec(text connstr, text sql [, bool fail_on_error]) dblink_exec(text connname, text sql [, bool fail_on_error]) dblink_exec(text sql [, bool fail_on_error])
If two arguments are present, the first is first assumed to be a specific connection name to use. If the name is not found, the argument is then assumed to be a valid connection string, of standard libpq format, e.g.: "hostaddr=127.0.0.1 dbname=mydb user=postgres password=mypasswd" If only one argument is used, then the unnamed connection is used.
dblink_open starts an explicit transaction. If, after using dblink_open, you use dblink_exec to change data, and then an error occurs or you use dblink_disconnect without a dblink_close first, your change *will* be lost.
select dblink_connect('dbname=dblink_test_slave'); dblink_connect ---------------- OK (1 row) select dblink_exec('insert into foo values(21,''z'',''{"a0","b0","c0"}'');'); dblink_exec ----------------- INSERT 943366 1 (1 row) select dblink_connect('myconn','dbname=regression'); dblink_connect ---------------- OK (1 row) select dblink_exec('myconn','insert into foo values(21,''z'',''{"a0","b0","c0"}'');'); dblink_exec ------------------ INSERT 6432584 1 (1 row) select dblink_exec('myconn','insert into pg_class values (''foo'')',false); NOTICE: sql error DETAIL: ERROR: null value in column "relnamespace" violates not-null constraint dblink_exec ------------- ERROR (1 row)