| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tracking SQLs that update data |
| Date: | 2010-06-15 03:30:09 |
| Message-ID: | 26246.1276572609@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Mon, Jun 14, 2010 at 5:55 PM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
>> 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.
Or, if you're worried about actions from functions, use a trigger to do
the logging. There are approximately no cases where a rule is really
better than a trigger :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M. Bashir Al-Noimi | 2010-06-15 03:45:51 | Does enterprisedb.com down? |
| Previous Message | M. Bashir Al-Noimi | 2010-06-15 03:15:47 | Re: Unable to install pg in Win (MVR error) |