I see, I am having practically the same problem... utilizing
partitioning idea
http://www.postgresql.org/docs/8.3/interactive/ddl-partitioning.html
by table inheritance.
I have prepared a post with some trigger and rule examples for you
On Apr 7, 8:27 pm, [EMAIL PROTECTED] (samantha mahindrakar)
wrote:
Hi
I have written a program that imputes(or rather corrects data) with in
my database.
Iam using a temporary table where in i put data from other partitoined
table. I then query this table to get the desired data.But the thing
On Apr 8, 2008, at 2:43 PM, Alvaro Herrera wrote:
samantha mahindrakar escribió:
Well instead of creating a temp table everytime i just created a
permanant table and insert the data into it everytime and truncate
it.
I created indexes on this permanent table too. This did improve the
Hi
The reason for using the temporary table is that i need this data
buffered somewhere so that i can use it for later computation. And the
fact that for each imputation i need to have historical data from 10
previous weeks makes it necessary to create something that can hold
the data. However
On Apr 9, 2008, at 6:41 PM, samantha mahindrakar wrote:
Hi
The reason for using the temporary table is that i need this data
buffered somewhere so that i can use it for later computation. And the
fact that for each imputation i need to have historical data from 10
previous weeks makes it
We store traffic data in the partitioned tables. But the problem is
that all this data is not correct. The data is corrupt, hence they
need to be corrected.
On Wed, Apr 9, 2008 at 10:31 PM, Erik Jones [EMAIL PROTECTED] wrote:
On Apr 9, 2008, at 6:41 PM, samantha mahindrakar wrote:
Hi
The
samantha mahindrakar wrote:
Iam using a temporary table where in i put data from other partitoined
table. I then query this table to get the desired data.But the thing
is this temporary table has to be craeted for every record that i need
to correct and there are thousands of such records that
samantha mahindrakar escribió:
So the program necessarily creates a temporary table evrytime it has
to correct a record. However this table is dropeed after each record
is corrected.
Perhaps it would be better to truncate the temp table instead.
Iam not sure if i can use a cursor to
Well instead of creating a temp table everytime i just created a
permanant table and insert the data into it everytime and truncate it.
I created indexes on this permanent table too. This did improve the
performance to some extent.
Does using permanant tables also bloat the catalog or hinder the
samantha mahindrakar escribió:
Well instead of creating a temp table everytime i just created a
permanant table and insert the data into it everytime and truncate it.
I created indexes on this permanent table too. This did improve the
performance to some extent.
Does using permanant tables
10 matches
Mail list logo
