|
15 | 15 | of data blocks (<literal>pages</literal>) on physical storage in order to
|
16 | 16 | organize data searches on ranges of summarized data that can be easily skipped
|
17 | 17 | on the base of search filters (see <ulink
|
18 |
| - url="https://www.postgresql.org/docs/9.5/static/brin-intro.html"><citetitle> |
| 18 | + url="https://www.postgresql.org/docs/current/brin-intro.html"><citetitle> |
19 | 19 | PostgreSQL documentation</citetitle></ulink> for further details on BRINs).
|
20 | 20 | As a consequence, BRINs result to be really small indexes (up to 1000 times
|
21 | 21 | than GiST ones), generally with lower a performance compared with a GiST one,
|
|
90 | 90 | <![CDATA[CREATE INDEX test_pos_idx USING BRIN ON test (pos);]]>
|
91 | 91 | </programlisting>
|
92 | 92 | <para>
|
93 |
| - By default, BRINs summarize block of 128 pages. The lower numbers |
94 |
| - of pages are specified, the higher granularity is reached during |
95 |
| - the searches, and performance's gap between GiST indexes and BRINs |
96 |
| - is lower (consider that BRINs size increases as well). Different |
97 |
| - summarizations can be used with the following command: |
| 93 | + By default, BRINs summarize blocks of 128 pages. The smaller the |
| 94 | + number of pages specified, the higher the granularity in searches, |
| 95 | + and the gap in performance between GiST indexes and BRINs will be |
| 96 | + decreased. Note that the size of the BRINs increases as well. |
| 97 | + Different summarizations can be specified with the following |
| 98 | + command: |
98 | 99 | </para>
|
99 | 100 | <programlisting>
|
100 | 101 | <![CDATA[CREATE INDEX test_pos_idx USING BRIN ON test (pos) WITH (pages_per_range = 16);]]>
|
|
0 commit comments