| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Robin <robinstc(at)live(dot)co(dot)uk> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: compliance with 21 cfr part 11 |
| Date: | 2013-12-05 06:57:35 |
| Message-ID: | CAOR=d=3r3XmBBVwsxTVtRe4On7FCC7=mZC1K-3gZQozbRoaVOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 4, 2013 at 9:15 PM, Robin <robinstc(at)live(dot)co(dot)uk> wrote:
> I have built big nationwide health databases, and other secure systems
> requiring traceback and auditability.
>
> The more you are able to make the required processes transparent to the end
> user, the happier they are and the fewer problems you have from a user
> acceptance perspective.
Well one of the example triggers in the plpgsql documentation is an
audit trigger. So you can do it, but you kinda have to build parts of
it yourself.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 吕晓旭 | 2013-12-05 08:46:33 | Fwd: Help！Why CPU Usage and LoadAverage Jump up Suddenly |
| Previous Message | Richard Dunks | 2013-12-05 05:08:46 | Re: Need help with upsert |