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

From Fabrízio de Royes Mello
Subject Re: Database Design: Maintain Audit Trail of Changes
Date
Msg-id CAFcNs+rDO5=q3W2Y6pgu-Y3hKuqHKdsHw-q0-ETz6YMQezY+9g@mail.gmail.com
Whole thread Raw
In response to Re: Database Design: Maintain Audit Trail of Changes  (Rich Shepard <rshepard@appl-ecosys.com>)
Responses Re: Database Design: Maintain Audit Trail of Changes  (Bèrto ëd Sèra <berto.d.sera@gmail.com>)
List pgsql-general

On Thu, Jan 3, 2013 at 2:50 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
>
>   There should not be many changes in these tables.

Ok.
 
>
> 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.

I understand it and for this reason I said to "use some strategy to purge old historical data *OR* make your audit tables partitioned"... 

regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Database Design: Maintain Audit Trail of Changes
Next
From: Thomas Kellerer
Date:
Subject: Re: Large number of rows in pg_type and slow gui (pgadmin) refresh