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.
