From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Nikolay Shaplov <n.shaplov@postgrespro.ru>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind
Date: Fri, 27 May 2016 15:05:58 -0400
Message-ID: <20160527190558.GA703687@alvherre.pgsql> (raw)
In-Reply-To: <1544707.j5kAjF95Mp@nataraj-amd64>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Nikolay Shaplov wrote:
> Story start from the point that I found out that a.m. can not forbid changing
> some of it's reloptions with ALTER INDEX command. That was not necessary
> before, because all reloptions at that existed at that time can be changed on
> fly. But now for bloom index it is unacceptable, because for changing bloom's
> reloptions for existing index will lead to index malfunction.
Hmm, this sounds like a bug to me. In BRIN, if you change the
pages_per_range option for an existing index, the current index
continues to work because the value used during the last index build is
stored in the metapage. Only when you reindex after changing the option
the new value takes effect.
I think Bloom should do likewise.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, n.shaplov@postgrespro.ru
Subject: Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind
In-Reply-To: <20160527190558.GA703687@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox