Re: Database Design: Maintain Audit Trail of Changes

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Database Design: Maintain Audit Trail of Changes
Date: 2013-01-03 16:50:58
Message-ID: alpine.LNX.2.00.1301030848120.5088@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2013-01-03 16:52:39 Re: Database Design: Maintain Audit Trail of Changes
Previous Message Jose Martinez 2013-01-03 16:25:41 Unable to reload postgresql.conf without restarting