On Fri, Aug 21, 2009 at 7:27 AM, Heikki
Linnakangas<heikki.linnakangas@enterprisedb.com> wrote:
> Greg Stark wrote:
>> It looks like right now if an indexam has amregurgitate
>> set but not amhasgettuple then weird things could happen.
>
> The combination (amregurgitate && !amhasgettuple) makes no sense, BTW.
> If an indexam has no gettuple function, there's no way it can return
> data from the index.
>
to have two columns that can conflict is not error prone? why not make
amhasgettuple an enum?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
