Re: [GENERAL] select for update not locking properly. - Mailing list pgsql-interfaces

From Joseph Shraibman
Subject Re: [GENERAL] select for update not locking properly.
Date
Msg-id 396E0DC8.D8CDF135@selectacast.net
Whole thread Raw
List pgsql-interfaces
Damn, I though having seperate Statement objects was supposed to take
care of that.

Peter can you confirm this?

Tom Lane wrote:
>
> Joseph Shraibman <jks@selectacast.net> writes:
> > OK here is the test program.
>
> I don't know Java hardly at all, but it looks like you've got ten
> threads in Java all issuing commands through a *single* connection
> to a single backend.  Postgres isn't going to lock those threads
> against each other for you ... it has no idea whatever that the
> sequence of commands it's seeing aren't all from one thread.
>
> You'd need to have ten separate connections to ten separate backends
> to get the behavior you're expecting.  Try putting the Connection
> objects into the Adder objects and firing them up at Adder creation.
>
>                         regards, tom lane

pgsql-interfaces by date:

Previous
From: Bob Kline
Date:
Subject: Re: DELETING ROW
Next
From: Joseph Shraibman
Date:
Subject: How do I use connection pooling?