BRIN indexes

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Cc: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Subject: BRIN indexes
Date: 2016-01-28 17:10:35
Message-ID: CANu8Fizzh4eUaY4b3aMqbYYZ6k9nrkOOBacmxjn3WUqrx0ACXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Reposting because I received no reply from a previous inquiry as "9.5 new
features".

With regard to BRIN indexes:

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?

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2016-01-28 17:29:22 Re: BRIN indexes
Previous Message Andreas Kretschmer 2016-01-28 17:04:15 Re: Replication Question