Re: Help with tracking!

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Đỗ 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 14:33:37
Message-ID: l2ndcc563d11004200733ub963d0c2o7a0c9125b8d1876b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 20, 2010 at 8:31 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Tue, Apr 20, 2010 at 6:11 AM, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> wrote:
>> On Tue, 2010-04-20 at 06:03 -0600, Scott Marlowe wrote:
>>> Wouldn't this work:
>>>
>>> alter user smarlowe set log_statement = 'all';
>>
>> IIRC it only works inside the given session (so it needs to be run each
>> time a query will be executed)
>
> Not true:
>
> psql
> show log_statement;
>  log_statement
> ---------------
>  none
> alter user smarlowe set log_statement = 'all';
> show log_statement;
>  log_statement
> ---------------
>  all
> \q
> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ozz Nixon 2010-04-20 14:52:56 Anyone use Python/ceODBC/PostgreSQL?
Previous Message Scott Marlowe 2010-04-20 14:31:47 Re: Help with tracking!