Skip site navigation (1) Skip section navigation (2)

Re: Serialization errors on single threaded request stream

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Serialization errors on single threaded request stream
Date: 2005-08-26 16:10:54
Message-ID: 9668.1125072654@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> The problem is this:  a single thread is submitting database updates through a middle tier which has a pool of connections.  There are no guarantees of which connection will be used for any request.  Each request is commited as its own database transaction before the middle tier responds to the requester, which then immediately submits the next request.  Nothing else it hitting the database.  We are getting serialization errors.

Hm.  Are you sure your middle tier is actually waiting for the commit
to come back before it claims the transaction is done?

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Kevin GrittnerDate: 2005-08-26 17:03:02
Subject: Re: Serialization errors on single threaded request
Previous:From: Kevin GrittnerDate: 2005-08-26 15:44:09
Subject: Serialization errors on single threaded request stream

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group