dblink_build_sql_insert(text relname,
int2vector primary_key_attnums,
integer num_primary_key_atts,
text[] src_pk_att_vals_array,
text[] tgt_pk_att_vals_array) returns textNote: The following description applies only to Postgres-XC
dblink module has not been tested with Postges-XC yet. Although there're no reason that dblink does not run in Postgres-XC, the development team leaves the test and the use of this module entirely to users.
This section is identical to the corresponding PostgreSQL reference manual.
Note: The following description applies only to PostgreSQL
dblink_build_sql_insert can be useful in doing selective
replication of a local table to a remote database. It selects a row
from the local table based on primary key, and then builds a SQL
INSERT command that will duplicate that row, but with
the primary key values replaced by the values in the last argument.
(To make an exact copy of the row, just specify the same values for
the last two arguments.)
Note: The following description applies only to Postgres-XC
dblink module has not been tested with Postges-XC yet. Although there're no reason that dblink does not run in Postgres-XC, the development team leaves the test and the use of this module entirely to users.
This section is identical to the corresponding PostgreSQL reference manual.
Note: The following description applies only to PostgreSQL
Name of a local relation, for example foo or myschema.mytab. Include double quotes if the name is mixed-case or contains special characters, for example "FooBar"; without quotes, the string will be folded to lower case.
Attribute numbers (1-based) of the primary key fields, for example 1 2.
The number of primary key fields.
Values of the primary key fields to be used to look up the local tuple. Each field is represented in text form. An error is thrown if there is no local row with these primary key values.
Values of the primary key fields to be placed in the resulting INSERT command. Each field is represented in text form.
Note: The following description applies only to Postgres-XC
dblink module has not been tested with Postges-XC yet. Although there're no reason that dblink does not run in Postgres-XC, the development team leaves the test and the use of this module entirely to users.
This section is identical to the corresponding PostgreSQL reference manual.
Note: The following description applies only to PostgreSQL
Returns the requested SQL statement as text.
Note: The following description applies only to Postgres-XC
dblink module has not been tested with Postges-XC yet. Although there're no reason that dblink does not run in Postgres-XC, the development team leaves the test and the use of this module entirely to users.
This section is identical to the corresponding PostgreSQL reference manual.
Note: The following description applies only to PostgreSQL
As of PostgreSQL 9.0, the attribute numbers in primary_key_attnums are interpreted as logical column numbers, corresponding to the column's position in SELECT * FROM relname. Previous versions interpreted the numbers as physical column positions. There is a difference if any column(s) to the left of the indicated column have been dropped during the lifetime of the table.
Note: The following description applies only to Postgres-XC
dblink module has not been tested with Postges-XC yet. Although there're no reason that dblink does not run in Postgres-XC, the development team leaves the test and the use of this module entirely to users.
This section is identical to the corresponding PostgreSQL reference manual.
Note: The following description applies only to PostgreSQL
SELECT dblink_build_sql_insert('foo', '1 2', 2, '{"1", "a"}', '{"1", "b''a"}');
dblink_build_sql_insert
--------------------------------------------------
INSERT INTO foo(f1,f2,f3) VALUES('1','b''a','1')
(1 row)