| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Subject: | Re: BRIN indexes |
| Date: | 2016-01-28 18:03:01 |
| Message-ID: | 56AA57D5.6000307@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/28/2016 09:41 AM, Melvin Davidson wrote:
> So, IOW, and the answer to my question is yes, it should be insured that
> all pages involved are physically adjacent (by design or by pre-sort)
> before creating a BRIN on them.
> Further to the point, it is self defeating to have more than one BRIN
> index on the table if the columns involved would have mutually
> non-adjacent pages.
> Therefore, it actually would be good to state that in the documentation,
> even it were just a comment.
BRIN indexes are best used on INSERT only tables with a sequence of
numbers as a PK or indexed column that will be queried against. At least
as I understand it.
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Felipe Santos | 2016-01-28 18:16:31 | Re: BRIN indexes |
| Previous Message | Melvin Davidson | 2016-01-28 17:41:08 | Re: BRIN indexes |