Re: [PATCH] Move all am-related reloption code intosrc/backend/access/[am-name] and get rid of relopt_kind for custom AM

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: [PATCH] Move all am-related reloption code intosrc/backend/access/[am-name] and get rid of relopt_kind for custom AM
Дата
Msg-id 20170326180212.6kdmzc6i2icsax6s@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM  (Nikolay Shaplov <dhyan@nataraj.su>)
Ответы Re: [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM  (Nikolay Shaplov <dhyan@nataraj.su>)
Re: [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM  (Nikolay Shaplov <dhyan@nataraj.su>)
Список pgsql-hackers
Nikolay Shaplov wrote:

> If I would think about it now: we always know how many options we will have. 
> So we can just pass this number to palloc and assert if somebody adds more 
> options then expected... What do yo think about it.

I think we need to preserve the ability to add custom options, because
extensions may want to do that.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Nikolay Shaplov
Дата:
Сообщение: Re: [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Valgrind failures caused by multivariate stats patch