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
--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
