Re: Finding out on exactly what I am stuck - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: Finding out on exactly what I am stuck
Date
Msg-id 49E32381.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: Finding out on exactly what I am stuck  (Péter Kovács <maxottovonstirlitz@gmail.com>)
List pgsql-admin
Péter Kovács <maxottovonstirlitz@gmail.com> wrote:
> 2009/4/13 Kevin Grittner <Kevin.Grittner@wicourts.gov>:
>> Péter Kovács <maxottovonstirlitz@gmail.com> wrote:
>>> I found the source of the problem: the client
>>> application made SQL calls in invalid sequences.

>> Could you share information about what you did, what you would like
>> or expect as an error message, and what you got instead?  It might
>> help us improve PostgreSQL.

> the same JDBC connection was used simultaneously (in
> multiple threads) for various selects and updates

That would do it, all right -- the JDBC spec says that applications
should not assume support for concurrent access by multiple threads.
The only exception I can recall offhand is that Statement.cancel may
be invoked by a separate thread.

Based on your report, who knows -- maybe we could guard against this
in the JDBC driver....

Thanks for the information.

-Kevin

pgsql-admin by date:

Previous
From: Péter Kovács
Date:
Subject: Re: Finding out on exactly what I am stuck
Next
From: Mike angelo
Date:
Subject: pg_dump file size