From: | Ofer Israeli <oferi(at)checkpoint(dot)com> |
---|---|
To: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Inserts or Updates |
Date: | 2012-02-12 10:48:48 |
Message-ID: | 217DDBC2BB1E394CA9E7446337CBDEF20102C056C1C3@il-ex01.ad.checkpoint.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Frank Lanitz wrote:
> Am 07.02.2012 18:40, schrieb Ofer Israeli:
>> Table 1:
>> 46 columns
>> 23 indexes on fields of the following types:
>> INTEGER - 7
>> TIMESTAMP - 2
>> VARCHAR - 12
>> UUID - 2
>>
>> 23 columns
>> 12 indexes on fields of the following types:
>> INTEGER - 3
>> TIMESTAMP - 1
>> VARCHAR - 6
>> UUID - 2
>
> Are you regularly updating all columns? If not, maybe a good idea to
> split the tables so highly updated columns don't effect complete
> line.
We're not always updating all of the columns, but the reason for consolidating all the columns into one table is for UI purposes - in the past, they had done benchmarks and found the JOINs to be extremely slow and so all data was consolidated into one table.
Thanks,
Ofer
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Lanitz | 2012-02-12 18:29:13 | Re: Inserts or Updates |
Previous Message | Peter van Hardenberg | 2012-02-11 19:52:28 | Re: random_page_cost = 2.0 on Heroku Postgres |