Re: WIP: Rework access method interface

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: WIP: Rework access method interface
Дата
Msg-id CAPpHfdvT9uEZdvDtpchw0vZFepeoBtMGPASDbogTqg4P-QMRnA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WIP: Rework access method interface  (Petr Jelinek <petr@2ndquadrant.com>)
Ответы Re: WIP: Rework access method interface  (Petr Jelinek <petr@2ndquadrant.com>)
Список pgsql-hackers
On Mon, Sep 7, 2015 at 9:17 PM, Petr Jelinek <petr@2ndquadrant.com> wrote:
On 2015-09-04 16:26, Alexander Korotkov wrote:

Attached patch is implementing this. It doesn't pretend to be fully
correct implementation, but it should be enough for proof the concept.
In this patch access method exposes another function: amvalidate. It
takes data structure representing opclass and throws error if it finds
it invalid.
This method is used on new opclass definition (alter operator family
etc. are not yet implemented but planned). Also, there is SQL function
validate_opclass(oid) which is used in regression tests.
Any thoughts?


This is starting to look good

Thanks!
 
However I don't like the naming differences between validate_opclass and amvalidate. If you expect that the current amvalidate will only be used for opclass validation then it should be renamed accordingly.

I'm not yet sure if we need separate validation of opfamilies.

Also GetIndexAmRoutine should check the return type of the amhandler.

Will be fixed.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
 

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Speed up Clog Access by increasing CLOG buffers
Следующее
От: Andres Freund
Дата:
Сообщение: Re: creating extension including dependencies