Re: WIP: Access method extendability

Teodor Sigaev <teodor@sigaev.ru>

From: Teodor Sigaev <teodor@sigaev.ru>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2015-09-01T15:50:29Z
Lists: pgsql-hackers
> In general pattern of generic WAL usage is following.
>
> 1) Start using generic WAL: specify relation

M-m, what about extensions which wants to use WAL but WAL record doesn't 
connected to any relation? For example, transaction manager or kind of FDW.

>
> GenericXLogStart(index);
>
> 2) Register buffers
>
> GenericXLogRegister(0, buffer1, false);
> GenericXLogRegister(1, buffer2, true);
>
> first argument is a slot number, second is the buffer, third is flag indicating
> new buffer

Why do we need a slot number? to replace already registered buffer?



-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/


Commits

  1. Support CREATE ACCESS METHOD

  2. Restructure index access method API to hide most of it at the C level.