Re: [PERFORM] temp table "on commit delete rows": transaction overhead

2010-04-06 Thread Artiom Makarov
2010/4/1 Bruce Momjian : > I think one of the problems is that we do the truncate even if the table > has not be touched by the query, which is poor behavior. Thank you for the support. Will be this problem registered? PS I see a workaround: switch off "on commit delete rows" on temp tables and

Re: [PERFORM] temp table "on commit delete rows": transaction overhead

2010-04-06 Thread Artiom Makarov
2010/3/30 Tom Lane : > I don't recall any operations at transaction start for such tables, > but there may be some. > Both in СommitTransaction(void) and PrepareTransaction(void) we can see PreCommit_on_commit_actions() call; Here PreCommit_on_commit_actions() case ONCOM

[PERFORM] temp table "on commit delete rows": transaction overhead

2010-03-30 Thread Artiom Makarov
Hi! We have a postgres database which accessed by clients app via PL/PGSQL stored procedures ( 8.4.1 on x86_64 ubuntu 8.04 server). For some reasons we use about 25 temp tables "on commit delete rows". It widely used by our SP. When temp tables with "on commit delete rows" exists, I can see a str