| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, John Lumby <johnlumby(at)hotmail(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| Date: | 2014-05-29 21:43:02 |
| Message-ID: | CAGTBQpZrufzDMmo95ak72sb=CnEwYGCNcJ1V-U3KGQUQXqQH=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, May 29, 2014 at 6:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Claudio Freire <klaussfreire(at)gmail(dot)com> writes:
>> Didn't fix that, but the attached patch does fix regression tests when
>> scanning over index types other than btree (was invoking elog when the
>> index am didn't have ampeeknexttuple)
>
> "ampeeknexttuple"? That's a bit scary. It would certainly be unsafe
> for non-MVCC snapshots (read about vacuum vs indexscan interlocks in
> nbtree/README).
It's not really the tuple, just the tid
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-05-29 21:49:07 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| Previous Message | Tom Lane | 2014-05-29 21:19:35 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-05-29 21:49:07 | Re: Extended Prefetching using Asynchronous IO - proposal and patch |
| Previous Message | Josh Kupershmidt | 2014-05-29 21:41:21 | Re: Odd uuid-ossp behavior on smew and shearwater |