Re: [BUGS] Serialization errors on single threaded request

2005-09-06 Thread Kevin Grittner
Never mind -- mystery solved. The framework is at fault, PostgreSQL is fine. The signal that the query is done can be returned to the client before the commit. We'll get that fixed. Thank you all for your patience. -Kevin ---(end of broadcast)--

Re: [BUGS] Serialization errors on single threaded request

2005-09-06 Thread Kevin Grittner
Sorry to have left this hanging so long, but I was off sick all last week. We started with the loglevel=2 option in the driver. We ran for a few seconds and got about 620KB of output, including 15 of these. I'm starting to pore over them, but I'm not sure what I'm loooking for. I've never re

Re: [BUGS] Serialization errors on single threaded request

2005-08-26 Thread Oliver Jowett
Kevin Grittner wrote: > I'm afraid I'm not familiar with a good way to capture the stream of > communications with the database server. If you could point me in the right > direction, I'll give it my best shot. tcpdump will do the trick (something like 'tcpdump -n -w some.output.file -s 1514 -

Re: [BUGS] Serialization errors on single threaded request

2005-08-26 Thread Kevin Grittner
Unfortunately, the original test environment has been blown away in favor of testing the 8.1 beta release. I can confirm that the problem exists on a build of the 8.1 beta. If it would be helpful I could set it up again on 8.0.3 to confirm. I THINK it was actually the tip of the 8.0 stable br

Re: [BUGS] Serialization errors on single threaded request stream

2005-08-26 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > What happens if the timestamp of the commit is an exact match for the > timestamp of the next transaction start? What is the resolution of > the time sampling? It's not done via timestamps: rather, each transaction takes a census of the transaction X

Re: [BUGS] Serialization errors on single threaded request

2005-08-26 Thread Kevin Grittner
I am absolutely sure that the database transaction is always terminated by invoking commit or rollback, and waiting for the method to come back, before the middle tier returns control to the client. A couple other potentially relevant facts are that these connections are doing all this work in

Re: [BUGS] Serialization errors on single threaded request stream

2005-08-26 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> 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 databas

[BUGS] Serialization errors on single threaded request stream

2005-08-26 Thread Kevin Grittner
I have an odd one here. I was unable to find it with a search of the mailing lists. I've spent a few hours trying to create a simple test case, but so far these simple cases aren't showing the problem. I want to make sure this isn't a know problem before investing more time trying to come up