Re: Race condition in - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Race condition in
Date
Msg-id 1093543794.5994.55.camel@localhost.localdomain
Whole thread Raw
In response to Race condition in org.postgresql.jdbc1.AbstractJdbc1Statement?  (jao@geophile.com)
Responses Re: Race condition in org.postgresql.jdbc1.AbstractJdbc1Statement?
List pgsql-jdbc
This code has been removed from the current CVS head.

Which version of the code are you looking at ?

Dave
On Thu, 2004-08-26 at 13:27, jao@geophile.com wrote:
> Cursor and statement names include the value of m_preparedCount:
>
>     m_statementName = "JDBC_STATEMENT_" + m_preparedCount++;
>
> and
>
>     m_cursorName = "JDBC_CURS_" + m_preparedCount++;
>
> m_preparedCount is static, and it looks like m_preparedCount++ should
> be synchronized:
>
>     // m_preparedCount is used for naming of auto-cursors and must
>     // be synchronized so that multiple threads using the same
>     // connection don't stomp over each others cursors.
>     private static int m_preparedCount = 1;
>     private synchronized static int next_preparedCount()
>     {
>         return m_preparedCount++;
>     }
>
> But next_preparedCount() is not used.
>
> Should the creation of statement and cursor names use next_preparedCount()
> instead of using m_preparedCount directly?
>
> Jack Orenstein
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
--
Dave Cramer
519 939 0336
ICQ # 14675561
www.postgresintl.com


pgsql-jdbc by date:

Previous
From: jao@geophile.com
Date:
Subject: Race condition in org.postgresql.jdbc1.AbstractJdbc1Statement?
Next
From: jao@geophile.com
Date:
Subject: Re: Race condition in org.postgresql.jdbc1.AbstractJdbc1Statement?