| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Panagiotis Pediaditis <pped(at)ics(dot)forth(dot)gr> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: debuging transactions |
| Date: | 2007-09-07 13:23:34 |
| Message-ID: | 46E150D6.8040502@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Panagiotis Pediaditis wrote:
> Greetings,
>
> I am debugging a large application that is based on transactions
> of long series of complex SQL queries. I was wondering, is there a way
> to monitor tables changed by the transaction before the transaction
> actually commits? Otherwise debugging seems impossible.
There are no changes until the transaction commits - at least not ones
visible from outside the transaction.
If you are writing plpgsql functions you can add various RAISE NOTICE
messages around the place.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SHARMILA JOTHIRAJAH | 2007-09-07 13:43:01 | CLOB support in postgresql |
| Previous Message | Ron Johnson | 2007-09-07 13:02:52 | Re: Column as arrays.. more efficient than columns? |