Thanks a lot for the reply!
The applications uses the jdbc driver with autocommit turned off,
commit and rollback. Do you know if the jdbc driver just starts
a new transaction as soon as the last one was ended with commit/
rollback ?
Yes, it does.
You have to explictly setAutocommit(true) in
Philipp Reisner <[EMAIL PROTECTED]> writes:
>762 ?S 0:00 /usr/lib/postgresql/bin/postmaster
>764 ?S 0:00 postgres: stats buffer process
>765 ?S 0:00 postgres: stats collector process
> 24872 ?S 0:00 postgres: sd sd 10.2.2.6 idle in tr
Philipp Reisner <[EMAIL PROTECTED]> writes:
> If I execute this query several times (I receive the correct result set),
> and then do an explain of the same query, the backend terminates with
> sig 11 !!!
Can you get us a debugger stack trace from the crash?
Also you should specify the platform y
Am Montag, 28. Juli 2003 11:41 schrieb Peter Eisentraut:
> Philipp Reisner writes:
> > Once in a while (about 3 times a day) one or more INSERTS/DELETES simply
> > go into the "waiting" state, and block the whole database. The only way
> > out is to terminate the client connection (i.e. to abort th
Philipp Reisner writes:
> Once in a while (about 3 times a day) one or more INSERTS/DELETES simply
> go into the "waiting" state, and block the whole database. The only way
> out is to terminate the client connection (i.e. to abort the blocked
> INSERT/DELETE query)
>
> Further investigation with
HI,
Executing a crashes postgresql.
If I execute this query several times (I receive the correct result set),
and then do an explain of the same query, the backend terminates with
sig 11 !!!
Sometimes it crashes by simply executing the query (without explain).
I looks a lot like if the crash h
Hi,
We use postgresql 7.2.1 (actually the Debian binary packet version
7.2.1-2woody2)
Our database load has more QUERIES than INSERT/DELETES. But we have a
sever problem with the wirting operations.
Once in a while (about 3 times a day) one or more INSERTS/DELETES simply
go into the "waiting" s
This problem is happening with libpq 7.4 too.
I believe we have a problem with libpq 7.3.3 with encryption. I
currently don't have a 7.3.3/ssl system running, but this has been
reported by Christian Ruediger Bahls, who traced it, and Dave Page.
When running pgAdmin3 over a ssl encrypted connect
