You raise two issues: 1) About SET standard_conforming_strings=on This is required and in fact as you say it is the default behavior since 9.1. This has nothing to do which locking.
2) You see exclusive locks. Which locks? Can you say more? On Saturday, 23 November 2013 05:53:02 UTC-6, Jayadevan M wrote: > > I am testing our web2py application with a few concurrent users. While > monitoring the database (PostgreSQL), I can see a number of exclusive > locks. The SQL is > SET standard_conforming_strings=on > Is this expected behaviour? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
