Skip site navigation (1)
Skip section navigation (2)
Another little question ... would using any sort of TEMP table help out, i.e. loading the unaggregated data into a TEMP table, aggregating the data via a SELECT INTO another TEMP table, and then finally INSERT ... SELECT into the master, aggregated, triggered table? It seems like this might be a win if A) the TEMP tables fit into memory, and B) the load data aggregates well. Worst case ( i.e. all unique data in the load) seems like it might take much longer, however, since I'm creating 2 new TEMP tables ....
Peripheral Links
Header And Logo
|
Site Navigation
Re: Bulk loading/merging
- From: "Worky Workerson" <worky(dot)workerson(at)gmail(dot)com>
- To: pgsql-performance(at)postgresql(dot)org
- Subject: Re: Bulk loading/merging
- Date: Fri, 26 May 2006 15:04:59 -0400
Another little question ... would using any sort of TEMP table help out, i.e. loading the unaggregated data into a TEMP table, aggregating the data via a SELECT INTO another TEMP table, and then finally INSERT ... SELECT into the master, aggregated, triggered table? It seems like this might be a win if A) the TEMP tables fit into memory, and B) the load data aggregates well. Worst case ( i.e. all unique data in the load) seems like it might take much longer, however, since I'm creating 2 new TEMP tables ....
- References:
- Bulk loading/merging
- From: Worky Workerson
- Bulk loading/merging
- Prev by Date: Bulk loading/merging
- Next by Date: Re: is it possible to make this faster?
- Previous by thread: Bulk loading/merging
- Next by thread: Re: Bulk loading/merging
- Indexes: