Re: Physical append-only tables

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Physical append-only tables
Date: 2016-11-24 09:13:30
Message-ID: CABUevEz39k-2hSQ9E+GnKMHhP1xju11_NO8JTCrH4LkPqmJKog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 24, 2016 at 2:26 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> On Mon, Nov 14, 2016 at 08:43:12PM +0000, Greg Stark wrote:
> > That said, I don't think the "maintain clustering a bit better using
> > BRIN" is a bad idea. It's just the bit about turning a table
> > append-only to deal with update-once data that I think is overreach.
>
> What if we used BRIN to find heap pages where the new row was in the
> page BRIN min/max range, and the heap page had free space. Only if that
> fails do we put is somewhere else in the heap.
>

That would certainly be useful. You'd have to figure out what to do in the
case of multiple conflicting BRIN indexes (which you shouldn't have in the
first place, but that won't keep people from having them), but other than
that it would be quite good I think.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2016-11-24 09:20:31 Re: Push down more full joins in postgres_fdw
Previous Message Etsuro Fujita 2016-11-24 08:51:50 Re: Push down more full joins in postgres_fdw