Hi, all,
David Parker wrote:
We ran into the need to use COPY, but our application is also in Java.
We wrote a JNI bridge to a C++ routine that uses the libpq library to do
the COPY. The coding is a little bit weird, but not too complicated -
the biggest pain in the neck is probably getting
People,
There are several hacks floating around that add COPY capabilities to
the pgjdbc driver. As they all are rather simple hacks, they have not
been included in the cvs yet, but they tend to work fine.
FWIW, Dave Cramer just added beta COPY capability to JDBC. Contact him on
the JDBC
On Tue, 3 May 2005, Josh Berkus wrote:
There are several hacks floating around that add COPY capabilities to
the pgjdbc driver. As they all are rather simple hacks, they have not
been included in the cvs yet, but they tend to work fine.
FWIW, Dave Cramer just added beta COPY capability
I'm converting an application to be using postgresql instead of oracle.
There seems to be only one issue left, batch inserts in postgresql seem
significant slower than in oracle. I have about 200 batch jobs, each
consisting of about 14 000 inserts. Each job takes 1.3 seconds in
Tim Terlegård wrote:
Just as on Oracle you would use SQL*Loader for this application, you
should use the COPY syntax for PostgreSQL. You will find it a lot
faster. I have used it by building the input files and executing
'psql' with a COPY command, and also by using it with a subprocess,
both
On 5/3/05, Tim Terlegård [EMAIL PROTECTED] wrote:
Just as on Oracle you would use SQL*Loader for this application, you
should use the COPY syntax for PostgreSQL. You will find it a lot
faster. I have used it by building the input files and executing
'psql' with a COPY command, and also
Howdy!
I'm converting an application to be using postgresql instead of oracle.
There seems to be only one issue left, batch inserts in postgresql seem
significant slower than in oracle. I have about 200 batch jobs, each
consisting of about 14 000 inserts. Each job takes 1.3 seconds in
postgresql
conn.setAutoCommit(false);
pst = conn.prepareStatement(INSERT INTO tmp (...) VALUES (?,?));
for (int i = 0; i len; i++) {
pst.setInt(0, 2);
pst.setString(1, xxx);
pst.addBatch();
}
pst.executeBatch();
conn.commit();
This snip takes 1.3 secs in postgresql. How can I lower that?
You're
On 5/2/05, Tim Terlegård [EMAIL PROTECTED] wrote:
Howdy!
I'm converting an application to be using postgresql instead of oracle.
There seems to be only one issue left, batch inserts in postgresql seem
significant slower than in oracle. I have about 200 batch jobs, each
consisting of about
On 5/2/05, Tim Terlegård [EMAIL PROTECTED] wrote:
Howdy!
I'm converting an application to be using postgresql instead of oracle.
There seems to be only one issue left, batch inserts in postgresql seem
significant slower than in oracle. I have about 200 batch jobs, each
consisting
: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] batch inserts are slow
conn.setAutoCommit(false);
pst = conn.prepareStatement(INSERT INTO tmp (...) VALUES
(?,?)); for
(int i = 0; i len; i++) {
pst.setInt(0, 2);
pst.setString(1, xxx);
pst.addBatch();
}
pst.executeBatch
[EMAIL PROTECTED] (Christopher Petrilli) writes:
On 5/2/05, Tim Terlegård [EMAIL PROTECTED] wrote:
Howdy!
I'm converting an application to be using postgresql instead of
oracle. There seems to be only one issue left, batch inserts in
postgresql seem significant slower than in oracle. I
12 matches
Mail list logo
