Using PgSQL in high volume and throughput problem - Mailing list pgsql-novice

From Nikola Milutinovic
Subject Using PgSQL in high volume and throughput problem
Date
Msg-id 4282EAF2.3000305@ev.co.yu
Whole thread Raw
Responses Re: Using PgSQL in high volume and throughput problem  (Josh Berkus <josh@agliodbs.com>)
Re: [JDBC] Using PgSQL in high volume and throughput problem  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-novice
Hi all.

This might be OT, especiallz since I do not have the actual data for
volume and throughput, but can give only "bystander" impression.

I might get on-board a project that deals with a high volume and high
throughput data crunching task. It will involve data pattern recognition
and similar stuff. The project is meant to run in Java and use Berkeley
DB, probably Apache Lucene.

Now, this is the juicy part. Due to high volume and high throughput,
data is actually stored in ordinary files, while Berkeley DB is used
only for indexes to that data!

Like I've said, I don't have the figures, but I was told that that was
the only way to make it work, everything else failed to perform. My
question, in your oppinion, can PgSQL perform in such a scenario? Using
JDBC, of course.

I do realize that PgSQL gives a lot of good stuff, but here the speed is
of essence. The previous project has stripped Java code to the bare
bones, regarding data structures, just to make it faster.

Nix.

pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: First plpgsql Script
Next
From: Vitaly Belman
Date:
Subject: Autocommit in Postgresql