Re: BRIN index and aborted transaction

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BRIN index and aborted transaction
Date: 2015-07-24 16:55:46
Message-ID: CANP8+j+t6xTdo-15z+wZ7NUmneCM4pyo4ZTV-+xUC3pNFoKNDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23 July 2015 at 19:59, Josh Berkus <josh(at)agliodbs(dot)com> wrote:

> On 07/23/2015 11:18 AM, Robert Haas wrote:
> > Cool. I'm not sure exactly what the right solution is either, but it
> > seems like the current situation could very well lead to degrading
> > index performance over time, with no way to put that right except to
> > rebuild the index completely. So it seems worth trying to improve
> > things.
>
> As a reality check, if that was the situation, it wouldn't be the only
> type of index to have that problem. Even our BTrees, with certain
> update patterns, need to be periodically rebuilt from scratch.
>

Agreed

> In other words, I don't think that fixing performance issues with BRIN
> indexes and frequenly-updated tables should be a blocker for 9.5. Not
> clear on whether we're considering this an open item or not.
>

Definitely not, though I think we should document a few things better here.
I'll do that.

--
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 Simon Riggs 2015-07-24 17:00:26 Re: Proposal for CSN based snapshots
Previous Message Petr Jelinek 2015-07-24 15:59:13 Re: creating extension including dependencies