delta/gitlab/gitlab-ce.git/db, branch fix/gb/remove-gitlab-ci-module

Use Gitlab::Database.with_connection_pool from !9192

2017-02-14T12:29:36+00:00

Disconnect the pool after done

2017-02-14T12:14:22+00:00

Use threads directly, introduce pool later:

2017-02-14T12:14:22+00:00

Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8987#note_22938402

Revert "Bump schema to pass `rake db:setup`"

2017-02-14T12:14:22+00:00

This reverts commit f2ed7cbc9b36b6ad9bcc714b271e98ead756b816.

Introduce ThreadedConnectionPool for customized pool

2017-02-14T12:14:22+00:00

This way we could reuse this pool for other migrations

Feedback:

* https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8987#note_22923350
* https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8987#note_22923365

Bump schema to pass `rake db:setup`

2017-02-14T12:14:22+00:00

Try this way to provide database connection

2017-02-14T12:13:54+00:00

Use IS FALSE for both pg and mysql; Handle connections

2017-02-14T12:13:54+00:00

by ourselves so that even if the setting has 1 connection
we could still use more connections.

Run two threads to improve migration running time

2017-02-14T12:13:54+00:00

Remove inactive default email services

2017-02-14T12:13:54+00:00

Note that we no longer generate this by default.
This is for clearing legacy default data.