This was done already as a workaround after identifying this problem. I just gave it as an example.
-----Original Message----- From: Vitalii Tymchyshyn [mailto:tiv...@gmail.com] Sent: Friday, November 12, 2010 5:54 PM To: Kyriacos Kyriacou Cc: pgsql-performance@postgresql.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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
