From: | Michael Ansley <Michael(dot)Ansley(at)intecsystems(dot)co(dot)uk> |
---|---|
To: | 'Loïc TREGOUËT' <loic(at)ext(dot)cri74(dot)org>, pgsql-admin(at)postgresql(dot)org |
Subject: | RE: view performance |
Date: | 2000-06-14 14:16:34 |
Message-ID: | 2D50E16224C8D311B183009027452B476AFCC8@INTEC003 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
If your tables are indexed on date, among other things, the performance
should be as good as it is now.
MikeA
>> -----Original Message-----
>> From: Loïc TREGOUËT [mailto:loic(at)ext(dot)cri74(dot)org]
>> Sent: 14 June 2000 13:26
>> To: pgsql-admin(at)postgresql(dot)org
>> Subject: [ADMIN] view performance
>>
>>
>> Hello ,
>>
>> I use a database to store log files . I have 2 Million
>> rows by year
>> .
>> I want the maximum of performance when i access them from
>> my web site so
>> i've started to make one table by year :
>> log2000 : contain all the log information of the year 2000
>> log 1999 : ..
>>
>> I think now it's a bad idea because when i want to select
>> on two table i
>> have :
>> column x is ambiguous !
>>
>> But if i use only one table , it will be a huge table i will lose
>> performance . Isn't it ?
>>
>> If i use view , i will not increase the performance
>> because it's just a
>> view and not a table properly . Isn't it ?
>>
>> Please help me , thanks
>>
>>
>> loic(at)ext(dot)cri74(dot)org
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-14 14:42:39 | Re: copy command and indexes |
Previous Message | Loïc TREGOUËT | 2000-06-14 12:26:11 | view performance |