Gerlite,
I ran the test program you submitted and it seems to run OK (other than
some duplicate key in index errors). What is the problem you are
seeing? Specifically what are you expecing to happen, and how does what
you are seeing differ from your expectatations.
thanks,
--Barry
Gerlits AndrXs wrote:
> Attached you'll find a simple multi-threaded example of a couple of
> SERIALIZABLE transactions. I hope, I'm not making a complete ass of myself,
> but it seems that the JDBC driver is unprepared to handle simultaneous
> SERIALIZABLE transactions.
>
> The table structure to test with is really simple:
>
> CREATE TABLE test (
> id integer UNIQUE NOT NULL
> );
>
> The program tries to access the database for the highest id available, then
> use it in a preparedstatement.
>
> (The reason we do that is to prepare for the worst DB server available, we
> know that there are other ways to do this in postgres.)
>
> It first opens the connections, stores them, than hands them to the threads.
>
> No connection is issued twice simultaneously.
>
> Please edit the variables at the top, but check not to have more
> InserterThreads than dbConnections.
>
> Thanks
> Andras Gerlits
>
>
> ------------------------------------------------------------------------
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly