Re: Tracking SQLs that update data

From: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Tracking SQLs that update data
Date: 2010-06-19 11:28:21
Message-ID: AANLkTinWBv28ozTNWfHhHwqV8u6LDEYYylxZCNgAPu9-@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> It's far easier to adjust the logging.
>
> psql mydb
> alter mydb set log_statement='mod';

Thanks Scott.

Two questions:

1. Will this log_statement='mod' be a permanent thing, or when I have
done my testing and identifying the problem SQL, I can set it back to
default so not too much logging is being done?

2. After this statement, how or where do I find the culprit SQL?

Thanks

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Page 2010-06-19 13:12:12 Re: Problem serving one-click installer to Syria
Previous Message Piero Campa 2010-06-19 10:13:47 Re: Access remote DB (outside local network) via PgAdmin