[GENERAL] temp tables remain after server restart

2005-08-31 Thread Hari Bhaskaran
Hi, one of our programs went haywire and created around 200,000 temp tables. In the end, I restarted the db, but the temporary tables are still around the query SELECT n.nspname, c.relname, c.relkind, c.relpages, c.reltuples FROM pg_class c LEFT JOIN pg_namespace n ON n.oid = c.relnamespace WHE

Re: [GENERAL] temp tables remain after server restart

2005-08-31 Thread Hari Bhaskaran
> What did you do, the old "kill -9 some random process" approach to > database management? The recommended ways of cancelling a session > wouldn't have caused this. I never said I kill -9 . I do pg_ctl stop BTW, drop cascade on the namespace seems to be working. create temp queries failed with

[GENERAL] pg_autovacuum taking locks on multiple tables at the same time

2006-10-09 Thread Hari Bhaskaran
This is causing a headache for us, if that is indeed true. So we have code that goes like begin; lock table t1; lock table t2; ... ... Of course within our own code, we do make sure things are always locked in the same order (so we wouldn't create deadlocks). We do, however, end up in deadloc

[GENERAL] Availability of pg_backend_pid() immediately after connection establishment

2006-11-02 Thread Hari Bhaskaran
Someone in this group mentioned a while back that pg_backend_pid() function works only after some 1/2 second after the connection has been established. This had something to do with the stats collector to make its sweep every .5 seconds?. Does anyone have more information on this? Any help i