From: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: pgsql-sql@postgresql.org
Subject: Experience with splitting a Table transparently
Date: Wed, 8 Jun 2005 12:30:10 +0200
Message-ID: <ED4E30DD9C43D5118DFB00508BBBA76EB16751@neptun.sonorys.at> (raw)
Hi,
I'm looking for people who have got experience at splitting a table with
heavy records into two relations.
In my case there exists one table with the mentioned heavy records. These
are processed by a statemachine. Thus a bunch of columns gets changed
several times in the livetime of one record. The text and blob colmns remain
unchanged. However due to Postgres# MVCC one changed record gets duplicated,
even if just one bit is changed. This makes us IO-performance problems.
I intend now to split the table in transport data (which stays constant) and
status data (which is changed several times).
I have then several options: Change all stored procedures to mathc the new
relations and keep the interface equal.
Or create a view with a bunch of RULES to show the procedures the 'original
table'.
What is best?
Who has done such bevore?
Will this help us in IO-terms?
thanks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: robert.koepferl@sonorys.at
Subject: Re: Experience with splitting a Table transparently
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB16751@neptun.sonorys.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox