| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | manugarciac <manugarciac(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Check what a transaction did in the past |
| Date: | 2010-02-16 16:31:11 |
| Message-ID: | 328.1266337871@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> manugarciac wrote:
>> I have an Idle in transaction that's really long. I suspect there is a
>> problem in my application, but I can't figure out where. If I new which
>> queries that transaction did in the past, it would really help me find the
>> problem. I know the transaction id, the process id, everything there is to
>> know, except the queries it did in the past. Is there any way to check this?
> Turn on log_statements and check the log.
Note that log_statements alone isn't much help. You'll want to add at
least %p to log_line_prefix so that you can relate entries in the log
to currently active transactions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2010-02-16 16:32:45 | Re: Having a plpgsql function return multiple rows that indicate its progress in a cursor like fashion |
| Previous Message | Alvaro Herrera | 2010-02-16 16:27:51 | Re: Check what a transaction did in the past |