Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Date: 2015-12-21 10:58:36
Message-ID: CANP8+j+xGN7VaaREy0MNMCDiB7+9JpacJs-Kv6tGyZxODwTyeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 December 2015 at 09:35, Peter Geoghegan <pg(at)heroku(dot)com> wrote:

> On Mon, Dec 21, 2015 at 1:24 AM, Simon Riggs <simon(at)2ndquadrant(dot)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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-12-21 11:03:10 Re: Let PostgreSQL's On Schedule checkpoint write buffer smooth spread cycle by tuning IsCheckpointOnSchedule?
Previous Message Haribabu Kommi 2015-12-21 10:33:36 Re: Parallel Aggregate