Re: JDBC Large ResultSet problem + BadTimeStamp Patch

From: Steve Wampler <swampler(at)noao(dot)edu>
To: Peter Mount <peter(at)retep(dot)org(dot)uk>
Cc: Joseph Shraibman <jks(at)selectacast(dot)net>, "pgsql-interfaces(at)postgreSQL(dot)org" <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: JDBC Large ResultSet problem + BadTimeStamp Patch
Date: 2000-10-11 18:27:40
Message-ID: 39E4B11C.204A69A3@noao.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

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(at)noao(dot)edu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-10-11 18:28:06 Re: TIOGA
Previous Message Bruce Momjian 2000-10-11 18:12:57 Re: TIOGA

Browse pgsql-interfaces by date

  From Date Subject
Next Message Joseph Shraibman 2000-10-11 18:56:41 Re: JDBC Large ResultSet problem + BadTimeStamp Patch
Previous Message Bruce Momjian 2000-10-11 18:10:23 Re: [PATCHES] PgAccess schema-diagram cleanup