Re: cyclical redundancy checksum algorithm(s)? - Mailing list pgsql-general

From Joachim Wieland
Subject Re: cyclical redundancy checksum algorithm(s)?
Date
Msg-id 20060928083015.GA2663@mcknight.de
Whole thread Raw
In response to Re: cyclical redundancy checksum algorithm(s)?  (John Sidney-Woollett <johnsw@wardbrook.com>)
Responses Re: cyclical redundancy checksum algorithm(s)?  (John Sidney-Woollett <johnsw@wardbrook.com>)
Re: cyclical redundancy checksum algorithm(s)?  (Bernhard Weisshuhn <bkw@weisshuhn.de>)
List pgsql-general
On Thu, Sep 28, 2006 at 07:09:43AM +0100, John Sidney-Woollett wrote:
> Why not use an update trigger on the affected tables to record a
> lastupdated timestamp value when the record is changed.

> Surely this is simpler thanks computing some kind of row hash?

It depends on how you define "change". With the triggers you propose an

UPDATE table SET col = col;

is a change because there was a write operation. Any hash function's output
would be "no change" because the actual data did not change. An update might
entail an expensive update of some external data so you might want to make
sure that data really got modified.

--
Joachim Wieland                                              joe@mcknight.de
                                                           GPG key available

pgsql-general by date:

Previous
From: "A. Kretschmer"
Date:
Subject: Re: Definition of return types for own functions?
Next
From: John Sidney-Woollett
Date:
Subject: Re: cyclical redundancy checksum algorithm(s)?