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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: 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 02:22:59
Message-ID: CAM3SWZQQZSc6AopshMGEKJ2r7Q3zin+L2UOPD9VfxD6RM4W8og@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 20, 2015 at 6:14 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Since BRIN indexes cannot be primary keys nor unique keys, it's hard to
> be convinced that the use case of a table with only BRIN indexes is
> terribly interesting.

I'm not convinced of that.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2015-12-21 02:48:18 Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table
Previous Message Alvaro Herrera 2015-12-21 02:14:46 Re: Optimizing away second VACUUM heap scan when only BRIN indexes on table