| From: | AI Rumman <rummandba(at)gmail(dot)com> |
|---|---|
| To: | Omar Mehmood <omarmehmood(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transaction logging in the form of SQL statements |
| Date: | 2010-01-12 04:26:22 |
| Message-ID: | 2a7905441001112026y337eda06yd96219ca0f0b7b4c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Use
log_min_duration_statement=0
at postgresql.conf file to log every statement.
On Tue, Jan 12, 2010 at 7:50 AM, Omar Mehmood <omarmehmood(at)yahoo(dot)com> wrote:
> Is there any way to enable transaction logging in the format of SQL
> statements for committed transactions only ? In other words, a way to log
> all the SQL statements (including START TRANSACTION and COMMIT statements)
> for all committed mod type statements (INSERT UPDATE DELETE etc).
>
> Thanks,
> Omar
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2010-01-12 04:40:47 | Re: Using a lock to avoid: could not open relation with OID |
| Previous Message | Yan Cheng Cheok | 2010-01-12 02:12:18 | Best Practice when Encounter Invalid Stored Procedure Parameters |