column updates - Mailing list pgsql-general

From Ben
Subject column updates
Date
Msg-id Pine.LNX.4.44.0410291215330.3308-100000@localhost.localdomain
Whole thread Raw
Responses Re: column updates  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
I'm designing a system where I'll be making frequent updates to rows, but
some columns will change far less frequently than others. All columns will
be read with equal frequency, though probably by means of a materialized
view. Updates will happen via a stored proc.

Which makes the most sense?

1. Blindly overwrite the value for all columns, even columns that haven't
changed.

2. Compare the current value and update each column at a time, leaving
unchanged columns alone.

3. Break out my tables more, so that infrequently updated columns are in
different tables.


I'm thinking that 1 and 2 are similar and less complex than 3, but might
result in more dead tuples. 2 and 3 will have to look up values before
updates can happen. I don't know if 2 has any advantage over 1. 1 is
certainly the simpliest.


pgsql-general by date:

Previous
From: Eric E
Date:
Subject: SELECT a value from various tables depending on a column value
Next
From: "Sally Ruggero"
Date:
Subject: Recommended Procedure for Archiving Table Data