From: | Edoardo Panfili <edoardo(at)aspix(dot)it> |
---|---|
To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: strange (maybe) behaviour of table lock |
Date: | 2006-12-08 19:30:41 |
Message-ID: | 4579BD61.2050509@aspix.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Marlowe wrote:
> On Fri, 2006-12-08 at 09:16, Edoardo Panfili wrote:
>> I have a question regarding a strange behaviour (for me, maybe that this
>> is desidered feature) of LOCK on tables. I am using postgres 8.2
>>
>> I have a servlet that uses connection pools.
>> The servlet do "LOCK table,table2,table3,table4"
>> then do some select (I am testing the code, I will put the update in the
>> future) an then I close instruction and connection.
>
> Before we go any further, what are you trying to accomplish by this
> lock? Perhaps there's a better "postgresqlish" approach than a table
> lock.
You are right, also Tom said that.
At a lower level of lock all goes well but I'd like to know what is
going wrong. This is a bug of my code (obviously) and I am investigating.
thak you
Edoardo
--
edoardo(at)aspix(dot)it
AIM: edoardopn
Jabber: edoardopa(at)talk(dot)google(dot)com
tel:075 9142766
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-12-08 19:35:17 | Re: Male/female |
Previous Message | dananrg | 2006-12-08 19:28:26 | TOAD-like query builder for PostgreSQL? |