Re: Help needed for reading postgres log : RE: Concurrency issue under very heay loads

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Help needed for reading postgres log : RE: Concurrency issue under very heay loads
Дата
Msg-id 20090721010017.GB32074@alvh.no-ip.org
обсуждение исходный текст
Ответ на Help needed for reading postgres log : RE: Concurrency issue under very heay loads  ("Raji Sridar (raji)" <raji@cisco.com>)
Список pgsql-general
Raji Sridar (raji) wrote:
> I would like some help in reading the postgres logs.
> Here is a snippet of the log.
> Auto commit seems to be set to false.
> But still the logs shows "CommitTransactionCommand" in debug mode.
> The same order number is given for multiple clients.
> Please see "CommitTransactionCommand" below for both "select ...for
> update" and "update..." SQLs and let me know if I am reading correctly
> that auto commit is actually effective.

CommitTransactionCommand is an internal function that has nothing to do
with a SQL-level COMMIT.  If there were a true transaction commit you'd
see a debug entry saying "CommitTransaction".

You seem to be barking up the wrong tree here.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

В списке pgsql-general по дате отправления:

Предыдущее
От: Steve Crawford
Дата:
Сообщение: Re: Server Backup: pg_dump vs pg_dumpall
Следующее
От: Phoenix Kiula
Дата:
Сообщение: Re: First query very slow. Solutions: memory, or settings, or SQL?