Splitting a table for performance reasons - Mailing list pgsql-sql

From KÖPFERL Robert
Subject Splitting a table for performance reasons
Date
Msg-id ED4E30DD9C43D5118DFB00508BBBA76EB1673D@neptun.sonorys.at
Whole thread Raw
List pgsql-sql
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)?


pgsql-sql by date:

Previous
From: Markus Bertheau
Date:
Subject: getting details about integrity constraint violation
Next
From: Jaime Casanova
Date:
Subject: Re: [GENERAL] index row size 2728 exceeds btree maximum, 27