[ADMIN] Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2

2012-07-04 Thread Akash Kodibail
Hi All, We have a reporting application to consume transactional log created by a billing system. The flow of data in ETL framework is from TRANSACTION_LOG->STAGING_TABLES->FACT_TABLES->AGGREGATE_TABLES. There are around 15 aggregate tables to be populated from these staging tables. Number of

[ADMIN] auto vacuum errors

2012-07-04 Thread Isabella Ghiurea
HI Gurus I'm seeing a issue with some temp tables in contrib_regression db , the auto vacuum job will not run for this tables due some files/QID's missing how can I fix this ? The temp tables are growing too fast and they don't get empty/clean-up...any tips ? I 'm running PGSQL 8.3.6 on RH

Re: [ADMIN] auto vacuum errors

2012-07-04 Thread Tom Lane
Isabella Ghiurea writes: > I'm seeing a issue with some temp tables in contrib_regression db , the > auto vacuum job will not run for this tables due some files/QID's > missing how can I fix this ? Um ... in general, autovacuum just silently ignores temp tables, because it doesn't have any

Re: [ADMIN] Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2

2012-07-04 Thread Craig Ringer
On 07/05/2012 02:30 AM, Akash Kodibail wrote: -Staging table population happens in expected time. Anywhere from 10-15 minutes for each process. -Aggregation process almost never completes which is a set of 15 insert queries. Entire process happens in a single commit (population of staging tab