From: Steve Wampler <swampler@noao.edu>
To: Peter Mount <peter@retep.org.uk>
Cc: Joseph Shraibman <jks@selectacast.net>
Cc: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgresql.org>
Subject: Re: JDBC Large ResultSet problem + BadTimeStamp Patch
Date: Wed, 11 Oct 2000 11:27:40 -0700
Message-ID: <39E4B11C.204A69A3@noao.edu> (raw)
References: <Pine.LNX.4.21.0010111901340.8388-100000@maidast.demon.co.uk>
Peter Mount wrote:
...
> Yes, there is a problem with multiple statements and transactions on the
> same connection when it comes to thread safety.
>
> The problem as I see it is two fold.
>
> 1: How to deal with two statements within one transaction. Related to this
> is the metadata methods that issue queries, how to deal with them while
> within a transaction.
>
> 2: Currently the JDBC Specs only have transactions supported at the
> Connection level, so I can't see how they thought that Statements could
> possibly run within their own transactions, unless they thought that a
> workaround of this is the use of batches.
Ah, that probably explains why I've seen "tuple arrived before metadata"
messages when I've got several apps talking through CORBA to a java app
that connects to postgres. Do I need to synchronize both inserts and
queries at the java app level to prevent this? (I was hoping that
the BEGIN/END block in a transaction would be sufficient, but this makes
it sound as though it isn't.)
--
Steve Wampler- SOLIS Project, National Solar Observatory
swampler@noao.edu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: swampler@noao.edu, peter@retep.org.uk, jks@selectacast.net
Subject: Re: JDBC Large ResultSet problem + BadTimeStamp Patch
In-Reply-To: <39E4B11C.204A69A3@noao.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox