Re: Reliable and fast money transaction design - Mailing list pgsql-general

From Tom Lane
Subject Re: Reliable and fast money transaction design
Date
Msg-id 6851.1188409422@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reliable and fast money transaction design  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Reliable and fast money transaction design
List pgsql-general
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tom Lane wrote:
>> "Joshua D. Drake" <jd@commandprompt.com> writes:
>>> SERIALIZABLE is really slow :).
>>
>> Say what?  If anything it's probably faster than READ COMMITTED, because
>> it doesn't take as many snapshots.  But the difference is likely down in
>> the noise anyway.

> Not in production it isn't.

Well, I can believe that specific applications might be slower overall
due to having to retry transactions that get serialization failures,
or perhaps because they take more locks to prevent such failures.
But it's not slower as far as the database engine is concerned.
If you think otherwise I'd like to see a test case.

            regards, tom lane

pgsql-general by date:

Previous
From: Jeff Amiel
Date:
Subject: SSL and crash woes.
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Reliable and fast money transaction design