thanks for your replying
>>I think with packing he was referring to simply having more values in
>>the same disk space by using int2 instead of int4. (half the storage space)
I see yes, the values I'm dealing with are a bit too large to do that but yes
good technique. Were they smaller I would
Zoolin Lin wrote:
Thank you for the reply
Primary table is all integers like:
date id | num1 | num2 | num3 | num4 | num5 | num6 | num7 | num 8
-
primary key is on date to num->6 columns
What ty
Thank you for the reply
>> Primary table is all integers like:
>>
>> date id | num1 | num2 | num3 | num4 | num5 | num6 | num7 | num 8
>> -
>> primary key is on date to num->6 columns
>
>>> What typ
Zoolin Lin wrote:
thanks for your reply
Primary table is all integers like:
date id | num1 | num2 | num3 | num4 | num5 | num6 | num7 | num 8
-
primary key is on date to num->6 columns
What typ
thanks for your reply
> Primary table is all integers like:
>
> date id | num1 | num2 | num3 | num4 | num5 | num6 | num7 | num 8
> -
> primary key is on date to num->6 columns
>>What types are num1-
Zoolin Lin wrote:
Hi,
I have database with a huge amount of data so i'm trying to make it
as fast as possible and minimize space.
One thing i've done is join on a prepopulated date lookup table to
prevent a bunch of rows with duplicate date columns. Without this I'd
have about 2500 rows per hou
Hi,
I have database with a huge amount of data so i'm trying to make it as fast as
possible and minimize space.
One thing i've done is join on a prepopulated date lookup table to prevent a
bunch of rows with duplicate date columns. Without this I'd have about 2500
rows per hour with the exact
