DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	b=l4afkMlQy0AD+GB0ytg6D9+1S+5jwH62foQD4uyqkO4iV7sEJy0cNg2EB8ZNbSy8sh
	S8HuoHEMzwtBGR63+TfRzDXZUReKL7tB1PaUTrYxp5nNJLmuC/OY0xu8hpmn1GOZZUoU
	2rOnFNu5ImtvTOia8xW7zKjvX8sWUU1onbdNM=
Message-ID: <4CDD62FF.4020009@gmail.com>
Date: Fri, 12 Nov 2010 17:53:35 +0200
From: Vitalii Tymchyshyn <tivv00@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: Kyriacos Kyriacou <kyriacosk@prime-tel.com>
CC: pgsql-performance@postgresql.org
Subject: Re: MVCC performance issue
References: <8BCBF9DB739F034B87FE7C7D30EAE55C279F054F@hqex2k.francoudi.com>
In-Reply-To: <8BCBF9DB739F034B87FE7C7D30EAE55C279F054F@hqex2k.francoudi.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

12.11.10 15:47, Kyriacos Kyriacou написав(ла):
> PROBLEM DECRIPTION
> ------------------
> As an example, consider updating the "live" balance
> of a customer for each phone call where the entire customer record has
> to be duplicated again and again upon each call just for modifying a
> numeric value!
>    
Have you considered splitting customer record into two tables with 
mostly read-only data and with data that is updated often? Such 1-1 
relationship can make a huge difference to performance in your case. You 
can even try to simulate old schema by using an updateable view.

Best regards, Vitalii Tymchyshyn