Re: Tracking SQLs that update data

Поиск
Список
Период
Сортировка
От Scott Marlowe
Тема Re: Tracking SQLs that update data
Дата
Msg-id AANLkTikTTNQuSU1VDv2sMXmDltv4opRCGoch2CAkbJ0_@mail.gmail.com
обсуждение исходный текст
Ответ на Tracking SQLs that update data  (Phoenix Kiula <phoenix.kiula@gmail.com>)
Ответы Re: Tracking SQLs that update data  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Tracking SQLs that update data  (Phoenix Kiula <phoenix.kiula@gmail.com>)
Список pgsql-general
On Mon, Jun 14, 2010 at 5:55 PM, Phoenix Kiula <phoenix.kiula@gmail.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';

В списке pgsql-general по дате отправления:

Предыдущее
От: Scott Marlowe
Дата:
Сообщение: Re: DDL partitioning with insert trigger issue
Следующее
От: "M. Bashir Al-Noimi"
Дата:
Сообщение: Re: Unable to install pg in Win (MVR error)