Jason Lees (National Express) wrote: > It might not Be CF thats causing the problem, its most likley the DB thats > escalating the Lock to a full table lock and thus preventing other users > from running the queries until the table is free.
Pretty much the only way to get a full table lock in PostgreSQL is to use a LOCK TABLE statement for PostgreSQL uses MVCC (a.k.a. better than row locking). Quite unlikely. > Also try moving the DB onto another server, as we had a simular problem, > with ingres and moving the CF app to a new server solved the problem. I am more thinking of a unixODBC issue (admittedly, I never was a fan of it). If you have plans to move to CF MX you might want to test if the concurrency is better with JDBC. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
