Postgres Pro
Downloads
Home   >   mailing lists

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

From Simon Riggs
Subject Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Date
Msg-id CANP8+j+xGN7VaaREy0MNMCDiB7+9JpacJs-Kv6tGyZxODwTyeg@mail.gmail.com
Whole thread Raw
In response to Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Tree view
On 21 December 2015 at 09:35, Peter Geoghegan <pg@heroku.com> wrote:
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.


AFAICS, this idea is workable and so I'd say "patches welcome" on it. 

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: Parallel Aggregate
Next
From: Heikki Linnakangas
Date:
Subject: Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?