Re: Index trouble with 8.3b4 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Index trouble with 8.3b4
Date
Msg-id 87hchf6bsx.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Index trouble with 8.3b4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Index trouble with 8.3b4  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Jeff Davis <pgsql@j-davis.com> writes:
>> On Sun, 2008-01-13 at 18:52 -0500, Tom Lane wrote:
>>> I wonder whether there are any other places that are silently assuming
>>> that heapscans start from page zero ...
>
>> I considered that question when implementing sync scans, but I could not
>> think of any specific areas of the code that would likely be affected.
>
> I went through all of the heap_beginscan calls in the code last night.
> pgstattuple was broken but AFAICS none of the other callers care about
> the visitation order.  I wonder though about third-party add-ons :-(

Perhaps we ought to have made heap_beginscan guarantee an ordered scan and
made synch scans be explicitly requested. That would have touched a lot of
lines but been more conservative. I'm not sure it's worth going back on it now
though.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication
support!


pgsql-hackers by date:

Previous
From: "Stephen Denne"
Date:
Subject: 8.3RC1 on windows missing descriptive Event handle names
Next
From: Gregory Stark
Date:
Subject: Re: to_char incompatibility