| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Raji Sridar (raji)" <raji(at)cisco(dot)com> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Help needed for reading postgres log : RE: Concurrency issue under very heay loads |
| Date: | 2009-07-21 01:00:17 |
| Message-ID: | 20090721010017.GB32074@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2009-07-21 01:36:41 | Re: First query very slow. Solutions: memory, or settings, or SQL? |
| Previous Message | Steve Crawford | 2009-07-21 00:03:30 | Re: Server Backup: pg_dump vs pg_dumpall |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devin Ben-Hur | 2009-07-21 01:13:43 | Re: Full text search with ORDER BY performance issue |
| Previous Message | Krade | 2009-07-21 00:25:02 | Re: Full text search with ORDER BY performance issue |