Re: Help with tracking!

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Đỗ Ngọc Trí Cường <seminoob(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Help with tracking!
Date: 2010-04-20 23:57:13
Message-ID: 4BCE3F59.30708@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 20/04/2010 10:33 PM, Scott Marlowe wrote:

>> psql
>> show log_statement;
>> log_statement
>> ---------------
>> all
>
> Note however that other sessions won't see the change. Only
> connections that come after the change will see it.

Also, as the OP wants to use it for auditing, it's worth noting that
it's trivial for the audited user to simply disable log_statement in a
session with a SET command.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-04-21 00:03:34 Re: Performance impact of log streaming replication
Previous Message Andy 2010-04-20 23:44:36 Re: Performance impact of log streaming replication