Same problem with postgis database backend when running a development
server.
среда, 30 июля 2014 г., 17:41:58 UTC+3 пользователь Jani Kajala написал:
>
> Hi,
>
> I have a problem with leaking Postgres DB connections even if I
> have CONN_MAX_AGE=0. Every time I start the server and stop it by
I'm also seeing this in two of our apps. Has anybody figured out a
solution? Running Django 1.7.11.
On Monday, November 23, 2015 at 4:36:23 PM UTC-5, Jon Sandness wrote:
>
> I'm seeing this same issue in OS X 10.11.1 - interestingly, the hang only
> occurs when I run migrations through Jenkins.
I'm seeing this same issue in OS X 10.11.1 - interestingly, the hang only
occurs when I run migrations through Jenkins. If I manually run the
command inside of a VirtualBox session, it works as expected.
Jon
On Friday, August 1, 2014 at 6:41:53 AM UTC-7, Jani Kajala wrote:
>
> Haven't tried (y
Haven't tried (yet), I'm new to Python & Django & Postgres, got on board
with Python 3.4.1 and Django 1.7c1. I'm starting to suspect this isn't
really Django related directly, since I can consistently reproduce the
problem following way: 1) Run e.g. test case, break it in debugger 2) Stop
debug
Does it work fine on django 1.6? It could be a regression.
On Wednesday, July 30, 2014 10:41:58 AM UTC-4, Jani Kajala wrote:
>
> Hi,
>
> I have a problem with leaking Postgres DB connections even if I
> have CONN_MAX_AGE=0. Every time I start the server and stop it by
> Ctrl+Break a DB connectio
Hi,
I have a problem with leaking Postgres DB connections even if I
have CONN_MAX_AGE=0. Every time I start the server and stop it by
Ctrl+Break a DB connection is leaked.
When I check from Postgres there is bunch of "idle" connections with
following content:
SELECT "django_migrations"."app",
6 matches
Mail list logo
