| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind |
| Date: | 2016-05-27 19:05:58 |
| Message-ID: | 20160527190558.GA703687@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2016-05-27 19:24:50 | Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind |
| Previous Message | Andres Freund | 2016-05-27 18:58:53 | Hard to maintain duplication in contain_volatile_functions_not_nextval_walker |