Transactions vs speed. - Mailing list pgsql-hackers

From mlw
Subject Transactions vs speed.
Date
Msg-id 3A60FF35.EDE3516C@mohawksoft.com
Whole thread Raw
Responses Re: Transactions vs speed.  (Alfred Perlstein <bright@wintelcom.net>)
Re: Transactions vs speed.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I have a question about Postgres:

Take this update:update table set field = 'X' ;


This is a very expensive function when the table has millions of rows,
it takes over an hour. If I dump the database, and process the data with
perl, then reload the data, it takes minutes. Most of the time is used
creating indexes.

I am not asking for a feature, I am just musing. 

I have a database update procedure which has to merge our data with that
of more than one third party. It takes 6 hours to run.

Do you guys know of any tricks that would allow postgres operate really
fast with an assumption that it is operating on tables which are not
being used. LOCK does not seem to make much difference.

Any bit of info would be helpful.

-- 
http://www.mohawksoft.com


pgsql-hackers by date:

Previous
From: Horst Herb
Date:
Subject: Re: CRCs
Next
From: Lamar Owen
Date:
Subject: Re: RPMs (was Re: Re: Beta2 ... ?)