Péter Kovács wrote:
> 2009/4/13 Kevin Grittner :
>> Péter Kovács 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 g
Reproducing the exact sequence of events would be very difficult.
Essentially, the same JDBC connection was used simultaneously (in
multiple threads) for various selects and updates, which is a bad
enough thing to do, I presume, as the connection instance is not
thread-safe. I don't think that much
Péter Kovács wrote:
> I found the source of the problem: the client
> application made SQL calls in invalid sequences.
> I ran the same test case against Oracle as well
> it gave a more informative error message ("protocol violation");
> and, also, the error message was emitted much closer to
Tom Lane wrote:
Kevin Bailey writes:
Just looking into an old 7.4 based server and the '\l' command isn't
showing a database called 'postgres' - template0 and template1 are there.
Is this expected on 7.4?
Yes. We didn't start creating a 'postgres' database by default unt
