Stephen Livesey wrote:
I am very new to PostgreSQL and have installed v7.03 on a Red Hat Linux
Server (v6.2), I am accessing the files using JDBC from a Windows 2000 PC.
I have created a small file as follows:
CREATE TABLE expafh (
postcode CHAR(8) NOT NULL,
postcode_record_no INT,
I am very new to PostgreSQL and have installed v7.03 on a Red Hat
Linux
Server (v6.2), I am accessing the files using JDBC from a Windows
2000 PC.
I have created a small file as follows:
CREATE TABLE expafh (
postcode CHAR(8) NOT NULL,
postcode_record_no INT,
street_name CHAR(30),
43 hours? Ouch, that is quite a long time! I'm no expert by any means, but
here are a few tips that I've picked up on this list that might help out:
1. The COPY command is blazing fast for importing, if you are certain your
input is clean, this is the way to go. Read more about that here:
Server (v6.2), I am accessing the files using JDBC from a Windows 2000 PC.
I don't use Microsoft software, nor Java, but a few general suggestions
for you:
- you may want to create the INDEX at the end (using CREATE INDEX)
in one operation
- you may want to run your requests in
At 02:25 PM 27-02-2001 -0500, Tom Lane wrote:
Is this sort of degradation normal using a PostgreSQL database?
No, it's not. Do you have any triggers or rules on this table that
I find slowdowns with inserts with rollbacks and updates with commits ( no
triggers or rules) :(.
But no
