On Fri, Aug 21, 2009 at 7:27 AM, Heikki Linnakangas<heikki.linnakan...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
