From: | "Kyriacos Kyriacou" <kyriacosk(at)prime-tel(dot)com> |
---|---|
To: | "Vitalii Tymchyshyn" <tivv00(at)gmail(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: MVCC performance issue |
Date: | 2010-11-12 16:18:18 |
Message-ID: | 8BCBF9DB739F034B87FE7C7D30EAE55C279F0551@hqex2k.francoudi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
This was done already as a workaround after identifying this problem.
I just gave it as an example.
-----Original Message-----
From: Vitalii Tymchyshyn [mailto:tivv00(at)gmail(dot)com]
Sent: Friday, November 12, 2010 5:54 PM
To: Kyriacos Kyriacou
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] MVCC performance issue
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Chobot | 2010-11-12 16:19:03 | Re: MVCC performance issue |
Previous Message | Kyriacos Kyriacou | 2010-11-12 16:14:00 | Re: MVCC performance issue |