From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Tracking SQLs that update data |
Date: | 2010-06-15 01:26:27 |
Message-ID: | AANLkTikTTNQuSU1VDv2sMXmDltv4opRCGoch2CAkbJ0_@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 14, 2010 at 5:55 PM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> Hi
>
> I'm having some issues with a code base where several different
> programs are updating one "status" column in the DB with their code.
> Mostly this is working, but in some cases the status column in a DB is
> getting updated when it shouldn't have been, and we're trying to
> locate which program did it.
>
> While checking through all the code, I'm also wondering if it is
> possible to somehow maintain a log of which SQL did the updating?
>
> My question: how can I set up a "RULE" so that when a specific column
> is updated, a separate table also logs which update SQL was issued?
It's far easier to adjust the logging.
psql mydb
alter mydb set log_statement='mod';
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2010-06-15 02:38:42 | Re: Tracking SQLs that update data |
Previous Message | Scott Marlowe | 2010-06-15 01:12:36 | Re: DDL partitioning with insert trigger issue |