Re: Database Design: Maintain Audit Trail of Changes - Mailing list pgsql-general

From Rich Shepard
Subject Re: Database Design: Maintain Audit Trail of Changes
Date
Msg-id alpine.LNX.2.00.1301030848120.5088@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Database Design: Maintain Audit Trail of Changes  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: Database Design: Maintain Audit Trail of Changes  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-general
On Thu, 3 Jan 2013, Fabrízio de Royes Mello wrote:

> And keep in mind that kind of table tend to grow quickly, so you must use
> some strategy to purge old historical data or make your audit table
> partitioned...

Fabrizio,

   There should not be many changes in these tables. And historical data
cannot be purged or the purpose of maintaining a history is lost. The
history is valuable for tracking changes over time in regulatory agency
staff and to prevent data manipulation such as was done several years ago by
the president of Southwestern Resources (a gold mining company) to pump up
the company's stock price by changing assay results.

Rich



pgsql-general by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Database Design: Maintain Audit Trail of Changes
Next
From: Rich Shepard
Date:
Subject: Re: Database Design: Maintain Audit Trail of Changes