| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Hannes Dorbath" <light(at)theendofthetunnel(dot)de>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index trouble with 8.3b4 |
| Date: | 2008-01-15 19:01:32 |
| Message-ID: | 87tzleq5f7.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Jeff Davis" <pgsql(at)j-davis(dot)com> writes:
> On Mon, 2008-01-14 at 22:10 -0500, Tom Lane wrote:
>> It's a tossup from here. Anybody have a strong opinion one way or the
>> other?
>
> To me a heapscan means "read all the tuples" (without implying order)
> and an ordered heap scan is a special case that should be made explicit.
> But this is not a strong opinion.
I had another thought. Perhaps in use_assert_checking mode we should have it
start from a random position every time. Or perhaps just a random position
from amongst the first n pages.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-15 19:22:31 | Re: Index trouble with 8.3b4 |
| Previous Message | Shane Ambler | 2008-01-15 18:53:07 | out of memory with INSERT INTO... SELECT... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-15 19:22:31 | Re: Index trouble with 8.3b4 |
| Previous Message | Jeff Davis | 2008-01-15 17:27:15 | Re: Index trouble with 8.3b4 |