Postgres contrib app creates a connection for _all_ configured DBs on ready.

[Curtis Maloney]

Whilst helping a client debug why a fresh deploy had created hundreds of connections, I stumbled upon this.

In django.contrib.postgres.apps.PostgresConfig the ready function iterates django.db.connections, checking if each connection has vendor == 'postgres'.

This creates a backend per configured DB. It then does nothing to close them afterwards.

This means the first connection to all DBs is once Django's setup is complete, not the first request.

The issue of not closing connections seems irrelevant, since django _should_ close them itself after requests; however, this is not the case for use of the ORM from other jobs [for instance, task queues].

It's also not unreasonable to believe there are cases where a system is built on the assumption DB connections will not be created until the first request. This expectation is violated by this code.

## Possible steps:

1. document this behavior - we should do this anyway
2. make the ready function _close_ connections once done.

I have begun a patch, and will implement the rest once someone agrees with this solution.

[Curtis Maloney]

Seems I misinterpreted this code, and it's creating DatabaseWrapper instances, but not necessarily connections. (calling it conn confused me).