| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, 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-21 00:10:26 |
| Message-ID: | 4BCE4272.9010503@pinpointresearch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Craig Ringer wrote:
> 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.
From the docs for log_statement: "Only superusers can change this
setting. "
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-04-21 00:20:23 | Re: Help with tracking! |
| Previous Message | Craig Ringer | 2010-04-21 00:03:34 | Re: Performance impact of log streaming replication |