diff options
| author | Nikolay Samokhvalov <gitlab@samokhvalov.com> | 2019-08-08 18:39:27 +0000 |
|---|---|---|
| committer | Nikolay Samokhvalov <gitlab@samokhvalov.com> | 2019-08-08 18:39:27 +0000 |
| commit | 0a8440eeff053137f4ef66da435f07c9e55dec2a (patch) | |
| tree | 3f3fe9148fab9bf43c45a1dd2ca2384a10ef2c9e | |
| parent | f9368d1d397bce32f6ed63451750f1f41a58c349 (diff) | |
| download | gitlab-ce-docs-nik-postgres-links-to-gitlab.tar.gz | |
Update understanding_explain_plans.mddocs-nik-postgres-links-to-gitlab
| -rw-r--r-- | doc/development/understanding_explain_plans.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/understanding_explain_plans.md b/doc/development/understanding_explain_plans.md index 20a4116386f..7c926c83a36 100644 --- a/doc/development/understanding_explain_plans.md +++ b/doc/development/understanding_explain_plans.md @@ -224,7 +224,7 @@ used when we would read too much data from an index scan, but too little to perform a sequential scan. A bitmap scan uses what is known as a [bitmap index](https://en.wikipedia.org/wiki/Bitmap_index) to perform its work. -The [source code of PostgreSQL](https://gitlab.com/postgres/postgres/blob/1c2cb2744bf3d8ad751cd5cf3b347f10f48492b3/src/include/nodes/plannodes.h#L446-L457) +The [source code of PostgreSQL](https://gitlab.com/postgres/postgres/blob/REL_11_STABLE/src/include/nodes/plannodes.h#L441) states the following on bitmap scans: > Bitmap Index Scan delivers a bitmap of potential tuple locations; it does not @@ -662,7 +662,7 @@ follow one of the other options below. ### Rails console -Using the [`activerecord-explain-analyze`](https://gitlab.com/6/activerecord-explain-analyze) +Using the [`activerecord-explain-analyze`](https://github.com/6/activerecord-explain-analyze) you can directly generate the query plan from the Rails console: ```ruby |