Skip site navigation (1) Skip section navigation (2)

Re: Inserts or Updates

From: Frank Lanitz <frank(at)frank(dot)uvena(dot)de>
To: Ofer Israeli <oferi(at)checkpoint(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Inserts or Updates
Date: 2012-02-12 18:29:13
Message-ID: 4F3804F9.4080607@frank.uvena.de (view raw or flat)
Thread:
Lists: pgsql-performance
Am 12.02.2012 11:48, schrieb Ofer Israeli:
> 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.

Ah... I see. Maybe you can check whether all of the data are really
needed to fetch with one select but this might end up in tooo much
guessing and based on your feedback you already did this step.

Cheers,
Frank

In response to

Responses

pgsql-performance by date

Next:From: Ofer IsraeliDate: 2012-02-12 18:32:11
Subject: Re: Inserts or Updates
Previous:From: Ofer IsraeliDate: 2012-02-12 10:48:48
Subject: Re: Inserts or Updates

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group