I have a very similar configuration and I get the exact same error.
Have you open a ticket? Thanks.
On Wednesday, December 18, 2013 2:23:57 AM UTC-8, Pavel Lurye wrote:
>
> Hi,
> CONN_MAX_AGE=None.
> Of course, restarting will fix the problem, but that's not what I'm
> expecting from django.
> I
Hi,
CONN_MAX_AGE=None.
Of course, restarting will fix the problem, but that's not what I'm
expecting from django.
I think this is django bug, but I want to be sure.
вторник, 17 декабря 2013 г., 18:59:46 UTC+4 пользователь Prashanth B
написал:
>
> I suspect restarting your Web server will fix it
I suspect restarting your Web server will fix it as you'll get fresh
connections. What is your CONN_MAX_AGE?
On Dec 17, 2013 4:57 AM, "Pavel Lurye" wrote:
> Hi,
> does anyone have used django1.6 persistent connections with postgresql?
> I've done a simple test and I'm not sure, that django behave
Hi,
does anyone have used django1.6 persistent connections with postgresql?
I've done a simple test and I'm not sure, that django behaves correctly.
Django can't recover after DB restart, and all further db requests lead to
server error:
---
Traceback (most recent call last):
File
"
4 matches
Mail list logo
