From: | Siddharth Jain <siddhsql(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to use the BRIN index properly? |
Date: | 2023-02-08 19:58:49 |
Message-ID: | CAPqV3pQCPas3CzMx-Syed_-Kzn_Vsq=b=H=_SgoXbFW58-mmWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
our insertion order is of course != index order otherwise the question
would have been trivial.
we use postgres 14
On Wed, Feb 8, 2023 at 11:51 AM Siddharth Jain <siddhsql(at)gmail(dot)com> wrote:
> Hello,
>
> We have large tables with billions of rows in them and want to take
> advantage of the BRIN index on them.
>
> Issues we are facing:
>
> - as I understand, BRIN index is useful only if the data is stored in
> index order. As an example we want to create a composite BRIN index on 3
> columns - integers and strings (varchar). How can we tell Postgres to store
> data in index order as new records are inserted into the database?
> - i understand that turning on autosummarize will keep the index fresh
> and up-to-date as new records are inserted. is this correct?
>
> Thanks for your help.
>
> S.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-02-08 20:27:29 | Re: How to use the BRIN index properly? |
Previous Message | Kirk Wolak | 2023-02-08 19:55:29 | Re: Sequence vs UUID |