On 02/03/2010 10:18 AM, Tom Lane wrote:
> Joe Conway writes:
>> The problem exists with all three dblink_build_sql_* functions. Here is
>> a more complete patch. If there are no objections I'll apply this to
>> HEAD and look at back-patching -- these functions have hardly been
>> touched since inc
Joe Conway writes:
> The problem exists with all three dblink_build_sql_* functions. Here is
> a more complete patch. If there are no objections I'll apply this to
> HEAD and look at back-patching -- these functions have hardly been
> touched since inception.
Do you really need to copy the relati
On 02/03/2010 04:49 AM, Rushabh Lathia wrote:
>
> create table foo (a int );
> postgres=# SELECT dblink_build_sql_insert('foo','1 2',2,'{\"0\",
> \"a\"}','{\"99\", \"xyz\"}');
> HINT: Use the escape string syntax for escapes, e.g., E'\r\n'.
> server closed the connection unexpectedly
The proble
On 02/03/2010 04:49 AM, Rushabh Lathia wrote:
> Testcase:
>
> create table foo (a int );
> postgres=# SELECT dblink_build_sql_insert('foo','1 2',2,'{\"0\",
> \"a\"}','{\"99\", \"xyz\"}');
> HINT: Use the escape string syntax for escapes, e.g., E'\r\n'.
> server closed the connection unexpectedly
Hi All,
Testcase:
create table foo (a int );
postgres=# SELECT dblink_build_sql_insert('foo','1 2',2,'{\"0\",
\"a\"}','{\"99\", \"xyz\"}');
HINT: Use the escape string syntax for escapes, e.g., E'\r\n'.
server closed the connection unexpectedly
This probably means the server terminated abno
