From: KÖPFERL Robert <robert.koepferl@sonorys.at>
To: pgsql-sql@postgresql.org
Subject: Splitting a table for performance reasons
Date: Thu, 2 Jun 2005 17:33:59 +0200
Message-ID: <ED4E30DD9C43D5118DFB00508BBBA76EB1673D@neptun.sonorys.at> (raw)
Hi,
I've got a table whose records are more less big. There's however jus one
Int-column changed frequently.
According to postgres' MVCC a whole record gets written, even if just one
bit was changed.
I think of splitting the table now in two parts, connected via the former
PK.
so like:
a|b|data | othercol | int -> a|b| data|othercol + a|int
Will this solve my ongoing performance problem?
Or is the overhead for referencial intergrity and system columns bigger than
what this gives?
BTW: How can I find out how many bytes a record consumes (having just fixed
size data)?
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: robert.koepferl@sonorys.at
Subject: Re: Splitting a table for performance reasons
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB1673D@neptun.sonorys.at>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB1673D@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