SQL logged during initial schema creation

[mboersma]

The change in #838 intends only to log SQL queries if DEIS_DEBUG was true, but it appears this flag is ignored when Django executes its initial DB management tasks:

DEBUG CREATE INDEX "guardian_userobjectpermission_417f1b1c" ON "guardian_userobjectpermission" ("content_type_id"); (params [])
DEBUG CREATE INDEX "guardian_userobjectpermission_8373b171" ON "guardian_userobjectpermission" ("permission_id"); (params [])
DEBUG CREATE INDEX "guardian_userobjectpermission_e8701ad4" ON "guardian_userobjectpermission" ("user_id"); (params [])
  Applying guardian.0001_initial... OK
DEBUG CREATE TABLE "django_session" ("session_key" varchar(40) NOT NULL PRIMARY KEY, "session_data" text NOT NULL, "expire_date" timestamp with time zone NOT NULL); (params None)
DEBUG CREATE INDEX "django_session_de54fa62" ON "django_session" ("expire_date"); (params [])
DEBUG CREATE INDEX "django_session_session_key_c0390e0f_like" ON "django_session" ("session_key" varchar_pattern_ops); (params [])
  Applying sessions.0001_initial... OK
[2016-06-30 21:57:55 +0000] [22] [INFO] Starting gunicorn 19.6.0
[2016-06-30 21:57:55 +0000] [22] [INFO] Listening at: http://0.0.0.0:8000 (22)
[2016-06-30 21:57:55 +0000] [22] [INFO] Using worker: sync
[2016-06-30 21:57:55 +0000] [25] [INFO] Booting worker with pid: 25
[2016-06-30 21:57:55 +0000] [28] [INFO] Booting worker with pid: 28

[arschles]

@mboersma can we move this out of the 2.2 milestone?

[arschles]

moving out of the 2.2 milestone