| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database Design: Maintain Audit Trail of Changes |
| Date: | 2013-01-03 17:27:42 |
| Message-ID: | CAFcNs+rDO5=q3W2Y6pgu-Y3hKuqHKdsHw-q0-ETz6YMQezY+9g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 3, 2013 at 2:50 PM, Rich Shepard <rshepard(at)appl-ecosys(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus de Oliveira | 2013-01-03 17:30:18 | Re: Unable to reload postgresql.conf without restarting |
| Previous Message | Rich Shepard | 2013-01-03 17:18:59 | Re: Database Design: Maintain Audit Trail of Changes |