-
Improvement
-
Resolution: Fixed
-
Minor
-
2.9, 3.1
-
MOODLE_29_STABLE, MOODLE_31_STABLE
-
MOODLE_32_STABLE
-
1. Successfully Install a new Moodle site on PostgreSQL
2. Units test and behat tests pass on PostgreSQLOptionally:
- Copy userquerytest.php
to your moodle root directory. - Open a terminal and go to your mooodle root directory and run the following command.
php userquerytest.php [NUMBER_OF_USERS_YOU_WANT](the higher number, the better)
- Compare the results to before and after the patch.
- Confirm that the results after the patch is at least the same or better than before the patch.
1. Successfully Install a new Moodle site on PostgreSQL 2. Units test and behat tests pass on PostgreSQL Optionally: Copy userquerytest.php to your moodle root directory. Open a terminal and go to your mooodle root directory and run the following command. php userquerytest.php [NUMBER_OF_USERS_YOU_WANT] (the higher number, the better) Compare the results to before and after the patch. Confirm that the results after the patch is at least the same or better than before the patch. - Copy userquerytest.php
Sharing some changes we've made to the postgresql DB driver over the years for performance reasons.
Most of the diff here revolves around adding the static table metadata caches back, and parsing queries for 'evil' things where we must reset to avoid stale data.
We've also ensured redundant LIMIT/OFFSET clauses are not added to queries; this helps the planner avoid a few bad cases, especially with OFFSET 0.
In a selection (non-sleeping) of unit tests, this patch alone cuts run time 15%.
Similar results may occur in e.g. upgrade scripts with many calls to update_record (see MDL-48604).
- has been marked as being related by
-
-
- Closed
-
- will be (partly) resolved by
-
-
- Closed
-
-
-
- Closed
-
- will help resolve
-
-
- Open
-