From: | "Arsalan Zaidi" <azaidi(at)directi(dot)com> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Turning off transactions completely. |
Date: | 2002-01-07 06:26:12 |
Message-ID: | 008e01c19744$3e1023e0$4301a8c0@directi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Well, every statement must be within a transaction, so to reduce the
number
> of transactions start one explicitly and commit when you're done. Then you
> only have one transaction for the whole thing.
>
I already do this. However, I don't want *any* transactions at all. I don't
care if I lose data in the middle of, say an update. The nature of the app
is such, that that data can be reconstructed.
However, as it currently stands, the app takes around 30 hrs to finish it's
run. I wish to reduce that to 24hr or less.
I found a comment from 1999 where someone asked a similiar Q and Mimijian
responded that that was not possible in pg. Is that still true? Can it be
easily changed in the code?
--Arsalan.
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-01-07 07:34:42 | Re: Turning off transactions completely. |
Previous Message | Ed Yu | 2002-01-07 05:02:09 | Re: create table with multiple unique fields |