Hi all, While investigating the causes of the deadlock I described previously, we noticed that ps output would often show some postgresql processes doing COMMIT. The developer in charge of the application(*) assures me that they are not using transactions (or at least not in any of the code he checked). My question is, would postgresql ps string show COMMIT at the end of INSERT/UPDATE even if explicit transactions are not used? (*)I am posting this on behalf of another department, so I am not entirely familiar with all the crap they have writing to the database (and, evidently, neither are they ;-)). I was called in as a resident postgresql guru. But these problems are so weird that I need to turn to the experts. At one point, they had a problem with pqxx library. It would create pqxxlog_condor table and write some crap there. This caused a huge performance problem, so eventually they disabled whatever option was causing it. However, yesterday I noticed pqxxlog_condor table in the database. It was empty, so I dropped it. I checked this morning and it's back again, also empty. Could COMMITs be coming from the library? thanks in advance, Eugene ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly
