From: | Edoardo Panfili <edoardo(at)aspix(dot)it> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, smarlowe(at)g2switchworks(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: strange (maybe) behaviour of table lock |
Date: | 2006-12-08 19:58:07 |
Message-ID: | 4579C3CF.7030501@aspix.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Edoardo Panfili <edoardo(at)aspix(dot)it> writes:
>> I spend many time to explain the bahaviour of the system:
>
>> I some occasions the system use another connection to retrieve some
>> information during the main connection. This explain the hangs but...
>> why sometimes the system works.
>
>> I do more tests.
>
> Try turning on statement logging in the server. Looking at the sequence
> of SQL commands actually issued to the server by the different clients
> would probably be informative.
I did some debug. I did non consider the execution of a second
transaction inside the first, this is my error.
The only way to avoid problem with my code is to lower the lock level, I
can't avoid the nesting of the transactions.
The systems works anyway two hours ago, I can't figure how to reproduce
that occasion.
thanks a lot to all
Edoardo
--
edoardo(at)aspix(dot)it
AIM: edoardopn
Jabber: edoardopa(at)talk(dot)google(dot)com
tel:075 9142766
From | Date | Subject | |
---|---|---|---|
Next Message | Brandon Aiken | 2006-12-08 20:05:00 | Re: concatenation operator || with "null" array |
Previous Message | Raymond O'Donnell | 2006-12-08 19:57:53 | Re: Male/female |