Re: Query on Postgres SQL transaction

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: Query on Postgres SQL transaction
Дата
Msg-id CAKAnmmJcMTxoD2ao8z8YXiU-9FspXZc9L+VKGrAYuig8mN3XSQ@mail.gmail.com
обсуждение исходный текст
Ответ на Query on Postgres SQL transaction  ("Bandi, Venkataramana - Dell Team" <Venkataramana.Bandi@dellteam.com>)
Ответы RE: Query on Postgres SQL transaction
Список 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 по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: PostGres ODBC too slow
Следующее
От: PetSerAl
Дата:
Сообщение: Single-User Mode oid assignment