Thanks for all the replies from different ppl.
As you pointed out, each INSERT/UPDATE operation will result in a TCP
round-trip delay for postgresql (may well true for all DBMS), this is the
big problem to challenge our requirements, as extensively modify the
(legacy) applicatioin is not a prefera
Stephen Frost wrote:
* Guoping Zhang ([EMAIL PROTECTED]) wrote:
Obviously, if there is no better solution, the TCP round trip penalty will
stop us doing so as we do have performance requirement.
Actually, can't you stick multiple inserts into a given 'statement'?
ie: insert into abc (123); in
In response to "Guoping Zhang" <[EMAIL PROTECTED]>:
>
> Thanks for pointing me the cause, but we simply cannot use the COPY FROM
> solution.
>
> Currently, our application service is running with its own dedicated local
> database, IF Feasible, we want to separate the application services out of
* Florian Weimer ([EMAIL PROTECTED]) wrote:
> * Stephen Frost:
> > Actually, can't you stick multiple inserts into a given 'statement'?
> > ie: insert into abc (123); insert into abc (234);
>
> IIRC, this breaks with PQexecParams, which is the recommended method
> for executing SQL statements nowa
* Stephen Frost:
> Actually, can't you stick multiple inserts into a given 'statement'?
> ie: insert into abc (123); insert into abc (234);
IIRC, this breaks with PQexecParams, which is the recommended method
for executing SQL statements nowadays.
--
Florian Weimer<[EMAIL PROTEC
* Guoping Zhang ([EMAIL PROTECTED]) wrote:
> Obviously, if there is no better solution, the TCP round trip penalty will
> stop us doing so as we do have performance requirement.
Actually, can't you stick multiple inserts into a given 'statement'?
ie: insert into abc (123); insert into abc (234);
* Guoping Zhang:
> Thanks for pointing me the cause, but we simply cannot use the COPY FROM
> solution.
Why not? Just do something like this:
CREATE TEMPORARY TABLE tmp (col1 TEXT NOT NULL, col2 INTEGER NOT NULL);
COPY tmp FROM STDIN;
row11
row22
...
\.
INSERT INTO target SELECT * FROM
Hi, Florian
Thanks for pointing me the cause, but we simply cannot use the COPY FROM
solution.
Currently, our application service is running with its own dedicated local
database, IF Feasible, we want to separate the application services out of
database server and run SEVERAL instances of applati
