| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 9.5 new features |
| Date: | 2016-01-25 06:53:29 |
| Message-ID: | n84gp1$vbv$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Melvin Davidson schrieb am 23.01.2016 um 16:27:
> http://www.postgresql.org/docs/9.5/interactive/brin-intro.html
>
> 62.1. Introduction
> ...
> "A block range is a group of pages that are physically adjacent in the table; for each block range, some summary info is stored by the index."
>
> From the above, may I presume that it is best to cluster (or sort),
> the table based on the intended BRIN column(s) before actually
> creating the index to insure the pages are adjacent? If so, should
> that not be included in the documentation, instead of implied?
>
That is something I am also curious about. If that was true, it would mean that BRIN indexes couldn't be used on tables that are not clustered along the index and it wouldn't make sense to have more than one BRIN index.
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2016-01-25 08:04:36 | Re: Performance options for CPU bound multi-SUM query |
| Previous Message | Christophe Pettus | 2016-01-25 05:25:04 | Re: ERROR: check constraint - PostgreSQL 9.2 |