Re: Query on Postgres SQL transaction - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Query on Postgres SQL transaction
Date
Msg-id CAKAnmmJcMTxoD2ao8z8YXiU-9FspXZc9L+VKGrAYuig8mN3XSQ@mail.gmail.com
Whole thread Raw
In response to Query on Postgres SQL transaction  ("Bandi, Venkataramana - Dell Team" <Venkataramana.Bandi@dellteam.com>)
Responses RE: Query on Postgres SQL transaction
List pgsql-general
That's a very vague question, but you can trace exactly what is happening by issuing 

SET log_statement = 'all';

Ideally at the session level by your application, but can also set it at the database and user level. If all else fails, set it globally (i.e. postgresql.conf). Turn it off again as soon as possible, it will make your logs extremely verbose. But you can track exactly what your application is doing.

Cheers,
Greg

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostGres ODBC too slow
Next
From: PetSerAl
Date:
Subject: Single-User Mode oid assignment