Re: BRIN index and aborted transaction
От | Simon Riggs |
---|---|
Тема | Re: BRIN index and aborted transaction |
Дата | |
Msg-id | CANP8+j+t6xTdo-15z+wZ7NUmneCM4pyo4ZTV-+xUC3pNFoKNDw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BRIN index and aborted transaction (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-hackers |
On 23 July 2015 at 19:59, Josh Berkus <josh@agliodbs.com> wrote:
Definitely not, though I think we should document a few things better here. I'll do that.
--
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.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: