| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index-only quals |
| Date: | 2009-08-21 17:28:33 |
| Message-ID: | 3073cc9b0908211028h6acca53bld3338ba8fda0b140@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 21, 2009 at 7:27 AM, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-08-21 17:30:35 | Re: Feedback about Drupal SQL debugging |
| Previous Message | Andrew Dunstan | 2009-08-21 17:17:11 | Re: Feedback about Drupal SQL debugging |