Please ignore that last message of mine.
The hanging problem was produced by an issue with the redis_cache.py
adapter failing to write a cache key.
El miércoles, 2 de mayo de 2018, 17:08:38 (UTC-3), Lisandro escribió:
>
> Well, I've commented out the line of the postgresql adapter of web2py, th
Well, I've commented out the line of the postgresql adapter of web2py, the
line where it runs the SET standard_conforming_strings=on; but now it hangs
in the previous line "SET CLIENT_ENCODING TO 'UTF8'".
This is the function of the web2py's adapter where the application hangs:
https://github.co
Hi there, sorry to bother in this old post.
I'm having a problem regarding standard_conforming_strings.
Today my app experienced a problem with Redis going out of memory.
After the problem was fixed, all my websites started to work normally,
except four of them (of a total of 260 websites).
For
We can make it optional. Please open a ticket.
On Sunday, 24 November 2013 02:28:23 UTC-6, Jayadevan M wrote:
>
> My doubt is - do we need to explicitly set it ON? Since the default
> setting is ON, any client connecting will have it turned ON anyway?
>
> On Sunday, November 24, 2013 1:48:23 PM U
My doubt is - do we need to explicitly set it ON? Since the default setting
is ON, any client connecting will have it turned ON anyway?
On Sunday, November 24, 2013 1:48:23 PM UTC+5:30, Massimo Di Pierro wrote:
>
> It must be done for every connection. Do you have connection pooling on?
> If a c
It must be done for every connection. Do you have connection pooling on? If
a connection is recycled it should not do it again.
On Saturday, 23 November 2013 22:49:47 UTC-6, Jayadevan M wrote:
>
> Thanks for the reply. OK, let us take this forward on the first one
> (default behaviour). Since th
Thanks for the reply. OK, let us take this forward on the first one
(default behaviour). Since the default behaviour is to SET
standard_conforming_strings=on, is there a need to do it again, for each
connection/call? It will incur an ever-so-small overhead which can be
avoided?
On Saturday, No
BTE, if you see an exclusive lock right on the
SET standard_conforming_strings=on
don't worry, it doesn't lock any tables.
On Saturday, November 23, 2013 3:01:00 PM UTC+1, Massimo Di Pierro wrote:
>
> You raise two issues:
>
> 1) About
> SET standard_conforming_strings=on
> This is required and i
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, Jayade
Is it possible to avoid this? Especially since the default server value is
ON since PostgreSQL 9.1
http://www.postgresql.org/docs/9.3/static/runtime-config-compatible.html
On Saturday, November 23, 2013 5:23:02 PM UTC+5:30, Jayadevan M wrote:
>
> I am testing our web2py application with a few co
10 matches
Mail list logo
