Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind
От | Alvaro Herrera |
---|---|
Тема | Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind |
Дата | |
Msg-id | 20160525180317.GA598084@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind (Nikolay Shaplov <n.shaplov@postgrespro.ru>) |
Ответы |
Re: [PROPOSAL] Move all am-related reloption code into
src/backend/access/[am-name] and get rid of relopt_kind
Re: [PROPOSAL] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind |
Список | pgsql-hackers |
Nikolay Shaplov wrote: > В письме от 25 мая 2016 13:25:38 Вы написали: > > Teodor Sigaev wrote: > > > >This all should me moved behind "access method" abstraction... > > > > > > +1 relopt_kind should be moved in am, at least. Or removed. > > > > Hm, but we have tablespace options too, so I'm not sure that using AM as > > abstraction level is correct. > We will use am for all indexes, and keep all the rest in relopotion.c for > non-indexes. May be divided options catalog into sections one section for each > kind. That makes sense. I can review the patch later. > And as I also would like to use this code for dynamic attoptions later, I > would like to remove relopt_kind at all. Because it spoils live in that case. As I remember, Fabrízio (in CC) had a patch for dynamic reloptions, but there was some problem with it and we dumped it; see https://www.postgresql.org/message-id/CAFcNs+rqCq1H5eXW-cvdti6T-xo2STEkhjREx=OdmAkK5tiOOw@mail.gmail.com for previous discussion. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: