From: Zeljko Trogrlic <zeljko@technologist.com>
To: khkachn@NOSPAMtoad.net
To: pgsql-interfaces@postgresql.org
Subject: Re: Performance issue with JDBC
Date: Mon, 11 Sep 2000 12:56:23 +0200
Message-ID: <4.1.20000911125539.0186e840@192.168.0.7> (raw)
In-Reply-To: <39B6BF69.E1AC723F@toad.net>
There is a "Fastpath" extension made for large objects. Try that.
At 00:04 7.9.2000 , Ken Kachnowich wrote:
>Hi,
>
> I am testing a Java application with the PostgreSQL JDBC that inserts
>a bunch of
>records into a database. Inserting 15 - 20 records every 10 seconds I
>find that
>the JDBC or Postgres can not keep up so I have a couple of questions.
>
>1) Where can I get the latest and greatest code for the JDBC? I
>downloaded
> the 7.0.2 PostgreSQL release and have been using the JDBC included
>there.
> Have there been any patches since that may help performaance?
>
>2) One of the fields inserted is a serialized Java object. I am saving
>it as a large
> object right now because I could not figure out how to get anything
>else to
> work. Could this be slowing things down? Is there a better way, such
>as
> into a bytea or varchar? Also where might I find some sample code to
>show
> me how to do it?
>
>3) Any other performance tips that may help me?
>
>Thanks,
>
>Ken K
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-interfaces@postgresql.org
Cc: zeljko@technologist.com, khkachn@NOSPAMtoad.net
Subject: Re: Performance issue with JDBC
In-Reply-To: <4.1.20000911125539.0186e840@192.168.0.7>
References: <39B6BF69.E1AC723F@toad.net> <4.1.20000911125539.0186e840@192.168.0.7>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox