my problem is back :(
ps shows a SELECT
i tried to cancel that blocking statement with |pg_cancel_backend|(pid).
after that ps show 'idle in transaction'. a simple kill pid doesn't
help. i did a pg_ctl -m immediate stop.
Postgres is away however the dead process is further present. I can stop
my problem is back :(
ps shows a SELECT
i tried to cancel that blocking statement with |pg_cancel_backend|(pid).
after that ps show 'idle in transaction'. a simple kill pid doesn't
help. i did a pg_ctl -m immediate stop.
Postgres is away however the dead process is further present. I can stop
Thomas Markus wrote:
my problem is back :(
ps shows a SELECT
i tried to cancel that blocking statement with |pg_cancel_backend|(pid).
after that ps show 'idle in transaction'. a simple kill pid doesn't
help. i did a pg_ctl -m immediate stop.
Postgres is away however the dead process is
Thomas Markus wrote:
thanks for your awnsers
i cant repeat the problem after increasing autovacuum_naptime to 5min. a
vacuumdb -f -a runs over night (and finished :) ) and now that blocking
statement finished after some seconds. it seems autovacuum = on is not
enough.
Enough for what?
the problem was not the long running statement. that statement has
blocked other connections and i was unable to drop that connection. at
the end all connections where blocked (output in ps: UPDATE waiting ..).
the only solution was to restart the server. After my understanding I
can terminate
I'm running 8.2.3 on ubuntu 6.06 (2.6.15-26-server SMP i686)
sometimes i have SELECTs that never ends. Normally I drop connections by
killing the connection process (kill PID). But these hanging
connections (which blocks other statements infinitly) cant be killed.
the only way is a pg_ctl -m
Thomas Markus wrote:
I'm running 8.2.3 on ubuntu 6.06 (2.6.15-26-server SMP i686)
sometimes i have SELECTs that never ends. Normally I drop connections by
killing the connection process (kill PID). But these hanging
connections (which blocks other statements infinitly) cant be killed.
On Wed, 2007-05-02 at 03:33, Thomas Markus wrote:
I'm running 8.2.3 on ubuntu 6.06 (2.6.15-26-server SMP i686)
sometimes i have SELECTs that never ends. Normally I drop connections by
killing the connection process (kill PID).
You shouldn't do that. You should issue a cancel query to the
thanks for your awnsers
i cant repeat the problem after increasing autovacuum_naptime to 5min. a
vacuumdb -f -a runs over night (and finished :) ) and now that blocking
statement finished after some seconds. it seems autovacuum = on is not
enough.
Thomas Markus schrieb:
I'm running 8.2.3
