Postgres Pro
Downloads
Home   >   mailing lists

Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Date
Msg-id CAM3SWZQNe8tAiq-533YawzERwpcDh+HFo0zjmWkY=ESSUXe4KQ@mail.gmail.com
Whole thread Raw
In response to Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
On Mon, Dec 21, 2015 at 1:24 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Given BRIN's characteristics, such a table design is compelling when the
> table is very large, yet possible only for certain use cases.

You can say the same thing about BRIN itself, of course.


-- 
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Next
From: Haribabu Kommi
Date:
Subject: Re: Parallel Aggregate