Thread: Postgres Processing Help !!!!
Hello to all, I have a problem with the use of temporary tables to have if somebody has an idea. Handling an application that it requires to process 6,000 registries Parents and the processing of each one requires to process N registries Children; Each teacher is sent to process in an own session (you do not synchronize) creating temporary tables and unloading them after which he finishes this session and he initiates with another one. The problem this in which the first registries soon process relatively fast but the response time grows exponentially and finally a considered process of 2 hours takes 14. And but it is that the about data base that when single initiating weighed 600 Mg turns to 12 GB. and after applying to him to a VACUUM and a REINDEX returns to 600 Mb. Somebody has an idea of because?. _________________________________________________________ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com
"Carlos Roberto Chamorro Mostac" <carlosrchamorro@yahoo.com> writes > Hello to all, I have a problem with the use of > temporary tables to have if somebody has an idea. > Handling an application that it requires to process > 6,000 registries Parents and the processing of each > one requires to process N registries Children; Each > teacher is sent to process in an own session (you do > not synchronize) creating temporary tables and > unloading them after which he finishes this session > and he initiates with another one. The problem this in > which the first registries soon process relatively > fast but the response time grows exponentially and > finally a considered process of 2 hours takes 14. And > but it is that the about data base that when single > initiating weighed 600 Mg turns to 12 GB. and after > applying to him to a VACUUM and a REINDEX returns to > 600 Mb. Somebody has an idea of because?. > Here is why - http://www.postgresql.org/docs/8.0/static/sql-vacuum.html Regards, Qingqing